Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 14 Jul 2021 13:21:31 +0000 (GMT)
From:   Holger Kiehl <Holger.Kiehl@dwd.de>
To:     Pavel Machek <pavel@denx.de>
cc:     Jiri Slaby <jirislaby@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
        patches@kernelci.org, lkft-triage@lists.linaro.org,
        jonathanh@nvidia.com, f.fainelli@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH 5.13 000/800] 5.13.2-rc1 review
In-Reply-To: <20210714104119.GA30649@amd>
Message-ID: <eb7845ca-985-e5af-39bd-a7d68ad57727@praktifix.dwd.de>
References: <20210712060912.995381202@linuxfoundation.org> <68b6051-09c-9dc8-4b52-c4e766fee5@praktifix.dwd.de> <YO56HTE3k95JLeje@kroah.com> <50fb4713-6b5d-b5e0-786a-6ece57896d2f@praktifix.dwd.de> <20653f1-deaa-6fac-1f8-19319e87623a@praktifix.dwd.de>
 <a59b73aa-24f6-7395-6b99-d6c62feb0fc4@kernel.org> <83b8a9a7-a29c-526-d36-78737cb9f56b@praktifix.dwd.de> <20210714104119.GA30649@amd>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

On Wed, 14 Jul 2021, Pavel Machek wrote:

> Hi!
> > 
> > > On 14. 07. 21, 10:15, Holger Kiehl wrote:
> > > >> Yes, will try to do that. I think it will take some time ...
> > > >>
> > > > Hmm, I am doing something wrong?
> > > 
> > > No, you are not: -rcs are not tagged.
> > > 
> > > >     git clone
> > > >     git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > >     linux-5.13.y
> > > >     cd linux-5.13.y/
> > > >     git tag|grep v5.13
> > > >     v5.13
> > > >     v5.13-rc1
> > > >     v5.13-rc2
> > > >     v5.13-rc3
> > > >     v5.13-rc4
> > > >     v5.13-rc5
> > > >     v5.13-rc6
> > > >     v5.13-rc7
> > > >     v5.13.1
> > > > 
> > > > There is no v5.13.2-rc1. It is my first time with 'git bisect'. Must be
> > > > doing something wrong. How can I get the correct git kernel rc version?
> > > 
> > > So just bisect v5.13.1..linux-5.13.y.
> > > 
> > But what do I say for bad?
> > 
> >    git bisect bad linux-5.13.y
> >    error: Bad rev input: linux-5.13.y
> > 
> > Just saying:
> > 
> >    git bisect bad
> >    git bisect good v5.13.1
> >    Bisecting: a merge base must be tested
> >    [62fb9874f5da54fdb243003b386128037319b219] Linux 5.13
> > 
> > If I read this correctly it now set v5.13 as bad and v5.13.1 as good.
> > How to set the correct bad?
> 
> You can use hashes instead of symbolic revisions, and that may be
> easier. I suspect you want to say "git bisect bad
> origin/linux-5.13.y". You can also just do git show and note the hash.
> 
> There's other option: git bisect can be quite confusing, but you are
> searching for a bug in linear history, so you can just git log
> --pretty=oneline into a file, then do the binary search
> manually. Should be 10 steps or so...
> 
Thanks! That 'git bisect bad origin/linux-5.13.y' got me going!

Holger