From: Dinh Nguyen <dinguyen@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Simon Schuster <schuster.simon@siemens-energy.com>
Cc: "Ethan Nelson-Moore" <enelsonmoore@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
workflows@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
dmaengine@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-iio@vger.kernel.org, Netdev <netdev@vger.kernel.org>,
linux-pci@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kbuild@vger.kernel.org,
"linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Alex Shi" <alexs@kernel.org>,
"Yanteng Si" <si.yanteng@linux.dev>,
"Dongliang Mu" <dzm91@hust.edu.cn>,
"Hu Haowen" <2023002089@link.tyut.edu.cn>,
"Kees Cook" <kees@kernel.org>, "Oleg Nesterov" <oleg@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Vinod Koul" <vkoul@kernel.org>, "Frank Li" <Frank.Li@kernel.org>,
"Dave Penkler" <dpenkler@gmail.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof WilczyDski" <kwilczynski@kernel.org>,
"Andreas Oetken" <andreas.oetken@siemens-energy.com>
Subject: Re: [PATCH] nios2: remove the architecture
Date: Tue, 19 May 2026 06:40:18 -0500 [thread overview]
Message-ID: <6b5378ed-270a-4ade-a944-654941ee9f8c@kernel.org> (raw)
In-Reply-To: <agxBqd-ubOL2_i-j@shikoro>
Hi Simon,
On 5/19/26 05:55, Wolfram Sang wrote:
> Hi Simon,
>
>>> ... but given this, you might want to get added in MAINTAINERS as
>>> reviewer (or even maintainer) for nios2? Besides that your efforts are
>>> already worth it in my book, it would also ensure you get CCed on
>>> patches like this. Then, you are not depending on people like Arnd
>>> putting you in the loop manually.
>>
>> Sure, I'd be glad to do so, but so far I refrained from it as I was a bit
>> unsure about the netiquette (can I simply do so by self-proclamation? At
>> least the git history seems to suggest so...).
>
> In your case, you can do so, I'd say. You explained your very reasonable
> interest in the architecture and have already shown efforts to keep it,
> as we can see from the git history. The final call will be done by Dinh
> Nguyen obviously with whom you probably need to sort out details. But I
> can't imagine your offer for help will be rejected, quite the contrary.
>
I 100% support adding you as a maintainer. Please send a patch.
Thanks,
Dinh
next prev parent reply other threads:[~2026-05-19 11:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 4:28 [PATCH] nios2: remove the architecture Ethan Nelson-Moore
2026-05-18 5:16 ` Wolfram Sang
2026-05-18 6:55 ` Uwe Kleine-König
2026-05-18 9:29 ` Arnd Bergmann
2026-05-18 10:57 ` Peter Zijlstra
2026-05-18 17:24 ` Simon Schuster
2026-05-18 20:46 ` Wolfram Sang
2026-05-19 0:13 ` Ethan Nelson-Moore
2026-05-19 10:30 ` Simon Schuster
2026-05-19 10:55 ` Wolfram Sang
2026-05-19 11:40 ` Dinh Nguyen [this message]
2026-05-19 11:07 ` Miguel Ojeda
2026-05-18 12:50 ` Krzysztof Kozlowski
2026-05-18 15:29 ` Jonathan Cameron
2026-05-19 8:48 ` David Laight
2026-05-19 9:43 ` Geert Uytterhoeven
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=6b5378ed-270a-4ade-a944-654941ee9f8c@kernel.org \
--to=dinguyen@kernel.org \
--cc=2023002089@link.tyut.edu.cn \
--cc=Frank.Li@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andreas.oetken@siemens-energy.com \
--cc=andrew+netdev@lunn.ch \
--cc=andy@kernel.org \
--cc=aneesh.kumar@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dmaengine@vger.kernel.org \
--cc=dpenkler@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=nuno.sa@analog.com \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=schuster.simon@siemens-energy.com \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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