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:40:45 +0300 [thread overview]
Message-ID: <YJULHXtTFD9wqQzq@atomide.com> (raw)
In-Reply-To: <fac6076d-5d2b-3165-b60a-b17a1ebbc506@leemhuis.info>
* Thorsten Leemhuis <linux@leemhuis.info> [210507 09:39]:
> On 07.05.21 11:35, Tony Lindgren wrote:
> > * Thorsten Leemhuis <linux@leemhuis.info> [210507 08:27]:
> >> 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!
> >
> > Hmm so the link above does not show where to git clone the regzb program
> > from? Or is that not yet published? Just wondering.
>
> The code is still very early WIP, so not yet published, but I'll publish
> the first few bits in a week or two, even if they are not yet useful to
> anyone besides myself. ;-)
OK thanks for the update.
Tony
prev parent reply other threads:[~2021-05-07 9:40 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
2021-05-07 9:35 ` Tony Lindgren
2021-05-07 9:39 ` Thorsten Leemhuis
2021-05-07 9:40 ` Tony Lindgren [this message]
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=YJULHXtTFD9wqQzq@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).