From: "Bjørn Mork" <bjorn@mork.no>
To: Giacinto Cifelli <gciofono@gmail.com>
Cc: Reinhard Speyerer <rspmn@t-online.de>,
netdev@vger.kernel.org, rspmn@arcor.de
Subject: Re: [PATCH] net: usb: qmi_wwan: added support for Thales Cinterion PLSx3 modem family
Date: Wed, 20 Jan 2021 14:13:45 +0100 [thread overview]
Message-ID: <87mtx3agza.fsf@miraculix.mork.no> (raw)
In-Reply-To: <CAKSBH7HbaVxyZJRuZPv+t2uBipZAkAYTcyJwRDy-UTB_sD4SJA@mail.gmail.com> (Giacinto Cifelli's message of "Wed, 20 Jan 2021 13:36:01 +0100")
Giacinto Cifelli <gciofono@gmail.com> writes:
> Hi Bjørn,
> I have fixed and resent, but from your comment I might not have
> selected the right line from maintaner.pl?
> what I have is this:
> $ ./scripts/get_maintainer.pl --file drivers/net/usb/qmi_wwan.c
> "Bjørn Mork" <bjorn@mork.no> (maintainer:USB QMI WWAN NETWORK DRIVER)
> "David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS)
> Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS)
> netdev@vger.kernel.org (open list:USB QMI WWAN NETWORK DRIVER)
> <<<< this seems the right one
> linux-usb@vger.kernel.org (open list:USB NETWORKING DRIVERS)
> linux-kernel@vger.kernel.org (open list)
>
> I have at the same time sent a patch for another enumeration of the
> same product, for cdc_ether. In that case, I have picked the
> following line, which also looked the best fit:
> linux-usb@vger.kernel.org (open list:USB CDC ETHERNET DRIVER)
>
> Did I misinterpret the results of the script?
Yes, but I'll be the first to admit that it isn't easy.
netdev is definitely correct, and the most important one.
But in theory you are supposed to use all the listed addresses. Except
that I don't think you need to CC David (and Jakub?) since they probably
read everything in netdev anyway. And I believe many (most?) people
leave out the linux-kernel catch-all, since it doesn't provide any extra
coverage for networking. At least I do.
Then there's the two remaining addresses. The linux-usb list is
traditionally CCed on patches touching USB drivers, since the USB
experts are there and not necessarily in netdev. And I'd like a copy
because that's the only way I'll be able to catch these patches. I
don't read any of the lists regularily.
This is my interpretation only. I am sure there are other opinions. But
as usual, you cannot do anything wrong. The worst that can ever happen
is that you have to resend a patch or miss my review of it ;-)
Bjørn
next prev parent reply other threads:[~2021-01-20 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 5:46 [PATCH] net: usb: qmi_wwan: added support for Thales Cinterion PLSx3 modem family Giacinto Cifelli
[not found] ` <20210118115250.GA1428@t-online.de>
2021-01-18 21:02 ` Bjørn Mork
2021-01-20 12:36 ` Giacinto Cifelli
2021-01-20 13:13 ` Bjørn Mork [this message]
2021-01-20 14:37 ` Giacinto Cifelli
2021-01-21 0:29 ` Jakub Kicinski
2021-01-20 4:56 ` Giacinto Cifelli
-- strict thread matches above, loose matches on Subject: below --
2021-01-26 4:41 Giacinto Cifelli
2021-01-26 4:46 ` Giacinto Cifelli
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=87mtx3agza.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=gciofono@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rspmn@arcor.de \
--cc=rspmn@t-online.de \
/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).