From: Tom Rini <trini@konsulko.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Kumar, Udit" <u-kumar1@ti.com>,
vigneshr@ti.com, nm@ti.com, joe.hershberger@ni.com,
m-chawdhry@ti.com, afd@ti.com, devarsht@ti.com, sjg@chromium.org,
emanuele.ghidoli@toradex.com, matthias.schiffer@ew.tq-group.com,
a-bhatia1@ti.com, vitor.soares@toradex.com, danishanwar@ti.com,
bmeng.cn@gmail.com, mkorpershoek@baylibre.com,
s-vadapalli@ti.com, u-boot@lists.denx.de,
joao.goncalves@toradex.com, hnagalla@ti.com
Subject: Re: [PATCH 0/4] Adding support to load secure firmware for HS devices
Date: Tue, 21 May 2024 13:23:52 -0600 [thread overview]
Message-ID: <20240521192352.GE2568172@bill-the-cat> (raw)
In-Reply-To: <ZkzuF_DIklnGd70_@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3896 bytes --]
On Tue, May 21, 2024 at 09:55:19PM +0300, Andy Shevchenko wrote:
> On Tue, May 21, 2024 at 11:52:47AM -0600, Tom Rini wrote:
> > On Tue, May 21, 2024 at 08:48:54PM +0300, Andy Shevchenko wrote:
> > > On Tue, May 21, 2024 at 10:45:41AM -0600, Tom Rini wrote:
> > > > On Tue, May 21, 2024 at 07:35:55PM +0300, Andy Shevchenko wrote:
> > > > > On Tue, May 21, 2024 at 10:21:45AM -0600, Tom Rini wrote:
> > > > > > On Tue, May 21, 2024 at 07:12:09PM +0300, Andy Shevchenko wrote:
> > > > > > > On Tue, May 21, 2024 at 08:59:17PM +0530, Kumar, Udit wrote:
> > > > > > > > On 5/21/2024 7:59 PM, Andy Shevchenko wrote:
> > > > > > > > > On Tue, May 21, 2024 at 04:26:44PM +0530, Udit Kumar wrote:
>
> ...
>
> > > > > > > > > Are you Cc'ing random people with this?
> > > > > > > > > Please don't do it.
> > > > > > > >
> > > > > > > > I used names names popped up while running get_maintainer.pl script of
> > > > > > > > u-boot
> > > > > > > >
> > > > > > > > your email id was there for patch-3 of this series
> > > > > > >
> > > > > > > Nice, the tool is broken. Please, work with the respective people to fix a tool
> > > > > > > or to tune it to avoid such mistakes in the future.
> > > > > > >
> > > > > > > (Hint: I would first disable Git fallback completely)
> > > > > >
> > > > > > So you were cc'd thanks to:
> > > > > > commit 5e541a05f70296dbad07fc1f4e8678ad207bb476
> > > > > > Author: Simon Glass <sjg@chromium.org>
> > > > > > Date: Sun Jul 30 21:01:45 2023 -0600
> > > > > >
> > > > > > env: Use include/env for text-environment includes
> > > > > >
> > > > > > The 'environment' word is too long. We mostly use 'env' in U-Boot, so use
> > > > > > that as the name of the include directory too.
> > > > > >
> > > > > > Signed-off-by: Simon Glass <sjg@chromium.org>
> > > > > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> # Intel Edison
> > > > >
> > > > > Yeah, and it even explicitly stated what I reviewed from that code...
> > > > >
> > > > > > Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> > > > > >
> > > > > > And, I'm sorry because there are other contributors who get upset when git
> > > > > > fallback doesn't find them (because it also ages out after a year).
> > > > > > In this case there's not even a "tweak the threshold" option since
> > > > > > there's only a single commit to the file so you're in 100% of them.
> > > > >
> > > > > Just an example of false positive by get_maintainer.pl :-(
> > > > > And a confirmation of what I said — tool is broken.
> > > >
> > > > It's an imperfect tool, yes. A quick check shows that if you never want
> > > > to be cc'd from a git tag, you can add yourself to
> > > > .get_maintainer.ignore and you will still be matched for things you have
> > > > an explicit MAINTAINER entry for.
> > >
> > > But this will kill me being a maintainer of U-Boot parts (regarding to
> > > a certain platform) which is not what I want.
> >
> > With a quick local test, no, it still reported you for edison stuff
> > since that's not where the ignore list comes in.
>
> I see. Still looking at the rate of false positives so far from U-Boot project
> I don't see that a big hammer, like the proposed one, should be used. Better to
> teach people on how to use/tune the tool, it will be helpful in a long-term.
Long term, it would be best if nearly everything had a real MAINTAINERS
entry. Short term, I don't know how to reconcile "I don't want to be
found via git history" with "Why wasn't I cc'd on a patch? Oh, because I
touched it more than a year ago? I don't like that!" in a way other
than:
- Encouraging people to add themselves to / expand existing MAINTAINERS
entries.
- Add themselves to the ignore list if they don't want to be found for
other contributions they made.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-05-21 19:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 10:56 [PATCH 0/4] Adding support to load secure firmware for HS devices Udit Kumar
2024-05-21 10:56 ` [PATCH 1/4] include: mach-k3: move k3 security functions to security.h Udit Kumar
2024-05-21 10:56 ` [PATCH 2/4] drivers: remoteproc: ti_k3 : enable secure booting with firmware images Udit Kumar
2024-05-21 10:56 ` [PATCH 3/4] include: env: ti: Add support for secure firmwares Udit Kumar
2024-05-21 10:56 ` [PATCH 4/4] mach-k3: common.c: add a flag for booting authenticated rproc binaries Udit Kumar
2024-05-21 14:29 ` [PATCH 0/4] Adding support to load secure firmware for HS devices Andy Shevchenko
2024-05-21 15:29 ` Kumar, Udit
2024-05-21 16:12 ` Andy Shevchenko
2024-05-21 16:21 ` Tom Rini
2024-05-21 16:35 ` Andy Shevchenko
2024-05-21 16:45 ` Tom Rini
2024-05-21 17:48 ` Andy Shevchenko
2024-05-21 17:52 ` Tom Rini
2024-05-21 18:55 ` Andy Shevchenko
2024-05-21 19:23 ` Tom Rini [this message]
2024-06-07 22:03 ` Tom Rini
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=20240521192352.GE2568172@bill-the-cat \
--to=trini@konsulko.com \
--cc=a-bhatia1@ti.com \
--cc=afd@ti.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bmeng.cn@gmail.com \
--cc=danishanwar@ti.com \
--cc=devarsht@ti.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=hnagalla@ti.com \
--cc=joao.goncalves@toradex.com \
--cc=joe.hershberger@ni.com \
--cc=m-chawdhry@ti.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=mkorpershoek@baylibre.com \
--cc=nm@ti.com \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=vitor.soares@toradex.com \
/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