From: Eliezer Tamir <eliezer.tamir@linux.intel.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Don Skidmore <donald.c.skidmore@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
e1000-devel@lists.sourceforge.net,
Eilon Greenstein <eilong@broadcom.com>,
Amir Vadai <amirv@mellanox.com>,
Eric Dumazet <erdnetdev@gmail.com>,
Willem de Bruijn <willemb@google.com>,
Eliezer Tamir <eliezer@tamir.org.il>
Subject: Re: [PATCH net-next v2 1/3] net: rename include/net/ll_poll.h to include/net/busy_poll.h
Date: Wed, 10 Jul 2013 17:00:48 +0300 [thread overview]
Message-ID: <51DD6910.80207@linux.intel.com> (raw)
In-Reply-To: <51DD5F05.6030206@broadcom.com>
On 10/07/2013 16:17, Arend van Spriel wrote:
> On 07/10/2013 02:13 PM, Eliezer Tamir wrote:
>> Rename the file and correct all the places where it is included.
>> Signed-off-by: Eliezer Tamir <eliezer.tamir@linux.intel.com>
>> ---
>> include/net/busy_poll.h | 183
>> +++++++++++++++++++++++
>> include/net/ll_poll.h | 183
>> -----------------------
>
> Did you use -M command line option with 'git format-patch'?
No, I'm using stg so I was not aware of the option.
If this is how we expect people to send patches, why isn't this the default.
I will resend shortly with -M
Thanks,
Eliezer
prev parent reply other threads:[~2013-07-10 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 12:13 [PATCH net-next v2 1/3] net: rename include/net/ll_poll.h to include/net/busy_poll.h Eliezer Tamir
2013-07-10 12:13 ` [PATCH net-next v2 2/3] net: rename ll methods to busy-poll Eliezer Tamir
2013-07-10 12:14 ` [PATCH net-next v2 3/3] net: rename busy poll socket op and globals Eliezer Tamir
2013-07-10 13:17 ` [PATCH net-next v2 1/3] net: rename include/net/ll_poll.h to include/net/busy_poll.h Arend van Spriel
2013-07-10 14:00 ` Eliezer Tamir [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=51DD6910.80207@linux.intel.com \
--to=eliezer.tamir@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=amirv@mellanox.com \
--cc=arend@broadcom.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=eilong@broadcom.com \
--cc=eliezer@tamir.org.il \
--cc=erdnetdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=willemb@google.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).