From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: linux-wireless@vger.kernel.org,
Ganapathi Kondraju <ganapathi.kondraju@silabs.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@kernel.org>,
Martin Fuzzey <martin.fuzzey@flowbird.group>,
Martin Kepplinger <martink@posteo.de>,
Marek Vasut <marex@denx.de>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>,
netdev@vger.kernel.org, Angus Ainslie <angus@akkea.ca>,
ganapathi.kondraju@silabs.com,
Amitkumar Karwar <amitkarwar@gmail.com>,
Siva Rebbagondla <siva8118@gmail.com>,
narasimha.anumolu@silabs.com, amol.hanwate@silabs.com,
shivanadam.gude@silabs.com, srinivas.chappidi@silabs.com
Subject: Re: [PATCH] wifi: rsi: Adding new driver Maintainers
Date: Tue, 31 Jan 2023 11:46:01 +0100 [thread overview]
Message-ID: <4019668.anssfa2V6d@pc-42> (raw)
In-Reply-To: <1675071591-7138-1-git-send-email-ganapathi.kondraju@silabs.com>
On Monday 30 January 2023 10:39:51 CET Ganapathi Kondraju wrote:
> Silicon Labs acquired Redpine Signals recently. It needs to continue
> giving support to the existing REDPINE WIRELESS DRIVER. Added new
> Maintainers for it.
>
> Signed-off-by: Ganapathi Kondraju <ganapathi.kondraju@silabs.com>
> ---
> MAINTAINERS | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Nitpick: usually, the subject of patches changing the MAINTAINERS
file is prefixed by "MAINTAINERS:".
--
Jérôme Pouiller
next prev parent reply other threads:[~2023-01-31 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 9:39 [PATCH] wifi: rsi: Adding new driver Maintainers Ganapathi Kondraju
2023-01-30 14:02 ` Marek Vasut
[not found] ` <DM6PR11MB44414FABE676E37C7F6FA0A0F2D19@DM6PR11MB4441.namprd11.prod.outlook.com>
2023-02-01 12:14 ` Jérôme Pouiller
2023-01-31 10:46 ` Jérôme Pouiller [this message]
2023-02-01 11:49 ` Johannes Berg
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=4019668.anssfa2V6d@pc-42 \
--to=jerome.pouiller@silabs.com \
--cc=amitkarwar@gmail.com \
--cc=amol.hanwate@silabs.com \
--cc=angus@akkea.ca \
--cc=ganapathi.kondraju@silabs.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marex@denx.de \
--cc=martin.fuzzey@flowbird.group \
--cc=martink@posteo.de \
--cc=narasimha.anumolu@silabs.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.krzyszkowiak@puri.sm \
--cc=shivanadam.gude@silabs.com \
--cc=siva8118@gmail.com \
--cc=srinivas.chappidi@silabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.