From: Nishanth Menon <nm@ti.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
broonie@kernel.org, mhocko@suse.cz, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mm-commits@vger.kernel.org, "Roger Quadros" <rogerq@kernel.org>,
linux-mtd@lists.infradead.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Tero Kristo" <kristo@kernel.org>
Subject: Re: mmotm 2022-02-08-15-31 uploaded (drivers/mtd/nand/raw/Kconfig)
Date: Wed, 9 Feb 2022 08:29:04 -0600 [thread overview]
Message-ID: <20220209142904.ye22csd2zh5vynik@stack> (raw)
In-Reply-To: <20220209150703.253b16bd@xps13>
On 15:07-20220209, Miquel Raynal wrote:
Hi Miquel,
> > > Maybe we should have added K3 people in Cc but their MAINTAINERS entry
> > > is incomplete so get_maintainers.pl did not immediately found them.
> >
> > What are we missing there?
>
> Actually nothing is missing, I overlooked the file name. I touched
> arch/arm64/Kconfig.platforms in my patch and of course
> get_maintainers.pl didn't look at the symbol owners. I should have
> checked that myself manually in the first place.
Sure. thanks for cross checking.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2022-02-09 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 23:31 mmotm 2022-02-08-15-31 uploaded Andrew Morton
2022-02-09 6:30 ` mmotm 2022-02-08-15-31 uploaded (drivers/mtd/nand/raw/Kconfig) Randy Dunlap
2022-02-09 8:03 ` Miquel Raynal
2022-02-09 13:54 ` Nishanth Menon
2022-02-09 14:07 ` Miquel Raynal
2022-02-09 14:29 ` Nishanth Menon [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=20220209142904.ye22csd2zh5vynik@stack \
--to=nm@ti.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=miquel.raynal@bootlin.com \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rogerq@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).