From: David Miller <davem@davemloft.net>
To: freddy@asix.com.tw
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, allan@asix.com.tw, louis@asix.com.tw
Subject: Re: [PATCH 1/1] [PATCH resubmit] ax88179_178a: Correct the RX error definition in RX header
Date: Tue, 22 Oct 2013 02:15:46 -0400 (EDT) [thread overview]
Message-ID: <20131022.021546.1648298758048784147.davem@davemloft.net> (raw)
In-Reply-To: <1382406449-2041-1-git-send-email-freddy@asix.com.tw>
Submit these, not individually as single patches, but as a patch set,
the first one with subject "[PATCH 1/2]" and the second with
subject "[PATCH 2/2]"
You have to do this, because it is absolutely essentially to let
me know which patch gets applies first and which one gets applied
second. The two patches are to the same file, so if you don't
tell me the order, they won't apply cleanly at all.
prev parent reply other threads:[~2013-10-22 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 1:47 [PATCH 1/1] [PATCH resubmit] ax88179_178a: Correct the RX error definition in RX header freddy
2013-10-22 6:15 ` David Miller [this message]
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=20131022.021546.1648298758048784147.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=allan@asix.com.tw \
--cc=freddy@asix.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=louis@asix.com.tw \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).