From: Wolfram Sang <wsa@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: mst@redhat.com, asowang@redhat.com,
Conghui <conghui.chen@intel.com>,
linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Jian Jun Chen <jian.jun.chen@intel.com>
Subject: Re: [PATCH] MAINTAINERS: Update maintainer list for virtio i2c
Date: Wed, 14 Dec 2022 11:20:34 +0100 [thread overview]
Message-ID: <Y5mjcuCRP45ynJis@shikoro> (raw)
In-Reply-To: <20221214063107.fazrfq3n26hw4ndl@vireshk-i7>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Hi Viresh,
> I understand that it is okay to pass the maintainership, within the
> company, for platform specific parts from one person to another, since
> they have the best knowledge of the code and are the only one
> interested in maintaining it too.
>
> But what is the rule for generic drivers like this one ?
Dunno if this is really a rule, but if a maintainer steps out and makes
sure there is someone to pick up the work, this is more than welcome.
Way better than a stale entry in the MAINTAINERS file.
I mean, it does not limit the chance to have further maintainers, for
example. I believe in meritocracy here. Those who do and collaborate,
shall get responsibility. If not, then not. We can fix this, too, if
needed.
What is the reason for your question?
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-14 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 5:36 [PATCH] MAINTAINERS: Update maintainer list for virtio i2c Conghui
2022-12-14 6:31 ` Viresh Kumar
2022-12-14 10:20 ` Wolfram Sang [this message]
2022-12-14 10:56 ` Viresh Kumar
2022-12-14 11:58 ` Michael S. Tsirkin
2022-12-14 12:00 ` Michael S. Tsirkin
2022-12-27 4:05 ` Chen, Jian Jun
2022-12-27 7:21 ` Michael S. Tsirkin
2022-12-14 11:37 ` Michael S. Tsirkin
2022-12-27 4:04 ` Chen, Jian Jun
2022-12-27 7:08 ` Michael S. Tsirkin
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=Y5mjcuCRP45ynJis@shikoro \
--to=wsa@kernel.org \
--cc=asowang@redhat.com \
--cc=conghui.chen@intel.com \
--cc=jian.jun.chen@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.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