From: Tony Lindgren <tony@atomide.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
"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 12:23:22 +0300 [thread overview]
Message-ID: <YJUHCpjsAY7ZnHjJ@atomide.com> (raw)
In-Reply-To: <e896704c-c13a-739d-0723-22fec35406ed@leemhuis.info>
Hi,
* Thorsten Leemhuis <linux@leemhuis.info> [210507 08:27]:
> 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
OK sent with a fixes and link tag. As a test, I sent it to the lists I
usually send patches to for this driver. The subject line is different,
and I left out all the extra Cc including you and regzb mailing list as
those are easy to forget to add to the mail. Let's see if regzb finds
the fix based on the Link or Fixes tag :)
Regards,
Tony
next prev parent reply other threads:[~2021-05-07 9:23 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 [this message]
2021-05-07 9:27 ` Naresh Kamboju
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=YJUHCpjsAY7ZnHjJ@atomide.com \
--to=tony@atomide.com \
--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=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=robh+dt@kernel.org \
--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).