netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Martin Habets <habetsm.xilinx@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org,
	ecree.xilinx@gmail.com, linux-net-drivers@amd.com
Subject: Re: [PATCH net] sfc: Add back mailing list
Date: Thu, 4 May 2023 11:10:49 +0300	[thread overview]
Message-ID: <20230504081049.GU525452@unreal> (raw)
In-Reply-To: <168318528134.31137.11625787711228662726.stgit@palantir17.mph.net>

On Thu, May 04, 2023 at 08:28:01AM +0100, Martin Habets wrote:
> We used to have a mailing list in the MAINTAINERS file, but removed this
> when we became part of Xilinx as it stopped working.
> Now inside AMD we have the list again. Add it back so patches will be seen
> by all sfc developers.

They are invited to join netdev community and read mailing list directly.

> 
> Signed-off-by: Martin Habets <habetsm.xilinx@gmail.com>
> ---
>  MAINTAINERS |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ebd26b3ca90e..dcab6b41ad8d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18987,6 +18987,7 @@ SFC NETWORK DRIVER
>  M:	Edward Cree <ecree.xilinx@gmail.com>
>  M:	Martin Habets <habetsm.xilinx@gmail.com>
>  L:	netdev@vger.kernel.org
> +L:	linux-net-drivers@amd.com

Is this open list or we will get bounce messages every time we send to it?

Thanks

>  S:	Supported
>  F:	Documentation/networking/devlink/sfc.rst
>  F:	drivers/net/ethernet/sfc/
> 
> 
> 

  reply	other threads:[~2023-05-04  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  7:28 [PATCH net] sfc: Add back mailing list Martin Habets
2023-05-04  8:10 ` Leon Romanovsky [this message]
2023-05-05  8:06   ` Martin Habets
2023-05-05  8:40 ` patchwork-bot+netdevbpf

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=20230504081049.GU525452@unreal \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=habetsm.xilinx@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).