From: David Miller <davem@davemloft.net>
To: crag0715@gmail.com
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, hayeswang@realtek.com,
mario_limonciello@dell.com, crag.wang@dell.com, sjg@chromium.org,
seanpaul@chromium.org, grundler@chromium.org,
david.chen7@dell.com, f.fainelli@gmail.com, jslaby@suse.cz,
gustavo@embeddedor.com,
charles.hyde@dell.corp-partner.google.com, bigeasy@linutronix.de,
zhongjiang@huawei.com
Subject: Re: [PATCH v2 1/1] r8152: sync sa_family with the media type of network device
Date: Sun, 21 Apr 2019 21:48:23 -0700 (PDT) [thread overview]
Message-ID: <20190421.214823.1067084318038589092.davem@davemloft.net> (raw)
In-Reply-To: <CAP-8N0jiguFSdyeop3rxMoNdYJemCRSdohyOR4z8B3HDmdUmng@mail.gmail.com>
From: Crag Wang <crag0715@gmail.com>
Date: Mon, 22 Apr 2019 11:17:49 +0800
> On Mon, Apr 22, 2019 at 10:44 AM David Miller <davem@davemloft.net> wrote:
>>
>>
>> Networking driver patches not sent to netdev@vger.kernel.org are very unlikely
>> to be integrated.
>>
>> Thank you.
>
> Adding netdev@vger.kernel.org to this email, sorry about missing the
> recipient in the first place.
This does not get the patch queued up in patchwork, nor allow other readers of
netdev to see the patch so that it can be properly reviewed.
You must make a new, fresh, posting of your patch.
next prev parent reply other threads:[~2019-04-22 4:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 2:23 [PATCH v2 1/1] r8152: sync sa_family with the media type of network device crag0715
2019-04-22 2:44 ` David Miller
2019-04-22 3:17 ` Crag Wang
2019-04-22 4:48 ` David Miller [this message]
2019-04-22 5:03 crag0715
2019-04-22 20:39 ` Jakub Kicinski
2019-04-23 2:52 ` Crag Wang
2019-04-22 21:29 ` Mario.Limonciello
2019-04-23 5:15 ` David Miller
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=20190421.214823.1067084318038589092.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bigeasy@linutronix.de \
--cc=charles.hyde@dell.corp-partner.google.com \
--cc=crag.wang@dell.com \
--cc=crag0715@gmail.com \
--cc=david.chen7@dell.com \
--cc=f.fainelli@gmail.com \
--cc=grundler@chromium.org \
--cc=gustavo@embeddedor.com \
--cc=hayeswang@realtek.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=netdev@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=sjg@chromium.org \
--cc=zhongjiang@huawei.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).