From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Tony Lindgren <tony@atomide.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
regressions@lists.linux.dev,
Benoit Cousson <bcousson@baylibre.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: #regzb introduced: 98feab31ac49 ("ARM: OMAP2+: Drop legacy platform data for dra7 sata")
Date: Fri, 7 May 2021 14:57:43 +0530 [thread overview]
Message-ID: <CA+G9fYsia4mfJpKXcz0Px3oDdsArHatqe0-rWWWC4iD47vj1oA@mail.gmail.com> (raw)
In-Reply-To: <e896704c-c13a-739d-0723-22fec35406ed@leemhuis.info>
On Fri, 7 May 2021 at 13:57, Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
> On 07.05.21 10:02, Tony Lindgren wrote:
> > * Naresh Kamboju <naresh.kamboju@linaro.org> [210506 15:19]:
> >> On Thu, 6 May 2021 at 17:23, Tony Lindgren <tony@atomide.com> wrote:
> >>> * Naresh Kamboju <naresh.kamboju@linaro.org> [210506 11:00]:
> >>>> Our bisect script pointed this as the first bad commit on linux
> >>>> mainline master branch.
> >>>> commit 98feab31ac491400f28b76a04dabd18ce21e91ba
> >>>> Author: Tony Lindgren <tony@atomide.com>
> >>>> Date: Wed Mar 10 14:03:51 2021 +0200
> >>>> ARM: OMAP2+: Drop legacy platform data for dra7 sata
> >>> Thanks for the report, looks like we are now missing the sata related
> >>> quirk flags compared to the patch above.
> >>> Below is a quick patch to add the missing quirk flags that might help
> >>> if you can give it a try.
> >> The reported problem was solved by this patch. Thank you.
> >> Please add reported and tested by tags.
> >> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> >> Tested-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> > OK good to hear and thanks for testing. Will send out a proper patch.
>
> Great to see that this is about to be fixed. And Naresh, many thx for
> giving the #regzb tag a try, even if regzbot (shameless plug for the
> unaware: https://linux-regtracking.leemhuis.info/post/regzbot-approach/
> ) is not up and running already, much appreciated!
>
> But FWIW, you don't need to add the tag to the subject; in fact, better
> use it for it's intended purpose. Instead add the tag to the mail's
> body, like this:
>
> #regzb introduced: 98feab31ac49 ("ARM: OMAP2+: Drop legacy platform data
> for dra7 sata")
Thanks for sharing more details about it.
Next time I will add this to the mail's body.
>
> Just ensure there is a blank line after that, as regzbot will have to
> deal with line breaks (as can be seen above) and somehow needs to decide
> where to stop. ;-)
Alright.
>
> Ohh, and Tony, if you want to do me a favour please include
>
> Link:
> https://lore.kernel.org/regressions/CA+G9fYtTN6ug3eBAW3wMcDeESUo+ebj7L5HBe5_fj4uqDExFQg@mail.gmail.com/
>
> in the commit message of the fix, then I have some real data already at
> hand to test regzbot in practice. :-D
- Naresh
next prev parent reply other threads:[~2021-05-07 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 11:00 #regzb introduced: 98feab31ac49 ("ARM: OMAP2+: Drop legacy platform data for dra7 sata") Naresh Kamboju
2021-05-06 11:53 ` Tony Lindgren
2021-05-06 15:18 ` Naresh Kamboju
2021-05-07 8:02 ` Tony Lindgren
2021-05-07 8:27 ` Thorsten Leemhuis
2021-05-07 9:23 ` Tony Lindgren
2021-05-07 9:27 ` Naresh Kamboju [this message]
2021-05-07 9:35 ` Tony Lindgren
2021-05-07 9:39 ` Thorsten Leemhuis
2021-05-07 9:40 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+G9fYsia4mfJpKXcz0Px3oDdsArHatqe0-rWWWC4iD47vj1oA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).