From: Li Zhong <zhong@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: linux-next@vger.kernel.org, dborkman@redhat.com, brouer@redhat.com
Subject: Re: [RFC PATCH net-next] packet: fix using smp_processor_id() in preemptible code
Date: Fri, 13 Dec 2013 06:54:55 +0800 [thread overview]
Message-ID: <1386888895.2586.5.camel@ThinkPad-T5421> (raw)
In-Reply-To: <20131211.164946.912458698857068460.davem@davemloft.net>
On Wed, 2013-12-11 at 16:49 -0500, David Miller wrote:
> Please send networking patches to netdev@vger.kernel.org, otherwise they
> will get lost.
>
Thank you for the reminder :)
Zhong
prev parent reply other threads:[~2013-12-12 1:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 6:10 [RFC PATCH net-next] packet: fix using smp_processor_id() in preemptible code Li Zhong
2013-12-11 9:55 ` Daniel Borkmann
2013-12-12 22:51 ` [PATCH v2 " Li Zhong
2013-12-12 7:19 ` Jesper Dangaard Brouer
2013-12-12 7:29 ` Daniel Borkmann
2013-12-12 21:15 ` David Miller
2013-12-13 1:49 ` Li Zhong
2013-12-12 23:55 ` [RFC PATCH " Li Zhong
2013-12-12 7:18 ` Jesper Dangaard Brouer
2013-12-13 6:41 ` Li Zhong
2013-12-13 7:40 ` Li Zhong
2013-12-11 21:49 ` David Miller
2013-12-12 22:54 ` Li Zhong [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=1386888895.2586.5.camel@ThinkPad-T5421 \
--to=zhong@linux.vnet.ibm.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.