From: David Miller <davem@davemloft.net>
To: amwang@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/3] netpoll: prepare for ipv6
Date: Thu, 03 Jan 2013 18:56:18 -0800 (PST) [thread overview]
Message-ID: <20130103.185618.1472655606309483969.davem@davemloft.net> (raw)
In-Reply-To: <1357267541-6433-1-git-send-email-amwang@redhat.com>
From: Cong Wang <amwang@redhat.com>
Date: Fri, 4 Jan 2013 10:45:39 +0800
> v3: fix CONFIG_IPV6=m case
You're talking about a change that isn't even present in this patch.
That's why people do "[PATCH 0/N]" cover postings with their
patch series, to collect information like this in the most
useful and relevent place.
Then I can check your patch set into a branch, and then do
a merge into my master branch and make the merge commit have
your cover letter as the commit message.
I'm not applying this series, submit it properly.
Thanks.
next prev parent reply other threads:[~2013-01-04 2:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 2:45 [PATCH net-next v3 1/3] netpoll: prepare for ipv6 Cong Wang
2013-01-04 2:45 ` [PATCH net-next v3 2/3] netpoll: add IPv6 support Cong Wang
2013-01-04 2:45 ` [PATCH net-next v3 3/3] netconsole: add IPv6 example in doc Cong Wang
2013-01-04 2:56 ` David Miller [this message]
2013-01-04 3:10 ` [PATCH net-next v3 1/3] netpoll: prepare for ipv6 Cong Wang
-- strict thread matches above, loose matches on Subject: below --
2013-01-04 3:14 [PATCH net-next v3 0/3] netpoll: add IPv6 support Cong Wang
2013-01-04 3:14 ` [PATCH net-next v3 1/3] netpoll: prepare for ipv6 Cong Wang
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=20130103.185618.1472655606309483969.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amwang@redhat.com \
--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).