Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: benjamin.poirier@gmail.com, luis.henriques@canonical.com,
	bhutchings@solarflare.com, nhorman@tuxdriver.com,
	netdev@vger.kernel.org, jcliburn@gmail.com
Subject: Re: [net PATCH] atl1c: Fix misuse of netdev_alloc_skb in refilling rx ring
Date: Wed, 31 Jul 2013 18:57:20 -0700	[thread overview]
Message-ID: <1375322240.10515.115.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130731.120126.2193837817631047825.davem@davemloft.net>

On Wed, 2013-07-31 at 12:01 -0700, David Miller wrote:

> I know, I realized this when I sent the pull request to Linus.
> 
> Eric, your patch submission format is extremely error prone for me
> sometime.  When you submit patches in email thread, and do things like
> you did here, it causes problems sometimes.
> 
> Really just send it in the usual way, with the real Subject line
> matching the commit message header line you wish to use etc.
> 

Sorry for that, I'll do this next times !

Thanks !

      reply	other threads:[~2013-08-01  1:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 16:47 [net PATCH] atl1c: Fix misuse of netdev_alloc_skb in refilling rx ring Neil Horman
2013-07-26 16:56 ` Luis Henriques
2013-07-26 17:02   ` Neil Horman
2013-07-26 22:56     ` David Miller
2013-07-27 16:25       ` Luis Henriques
2013-07-27  0:02 ` Ben Hutchings
2013-07-27  0:24   ` Ben Hutchings
2013-07-27 19:30     ` Luis Henriques
2013-07-27 19:49       ` Eric Dumazet
2013-07-27 21:30       ` Ben Hutchings
2013-07-27 23:59         ` Eric Dumazet
2013-07-28  3:02           ` David Miller
2013-07-28 10:44             ` Neil Horman
2013-07-28 16:15               ` Eric Dumazet
2013-07-28 18:53                 ` Neil Horman
2013-07-28 19:21                   ` Eric Dumazet
2013-07-28 20:08                     ` Eric Dumazet
2013-07-28 20:22                   ` Ben Hutchings
2013-07-28 23:01                     ` Eric Dumazet
2013-07-28 23:20                       ` Eric Dumazet
2013-07-28 23:25                         ` Eric Dumazet
2013-07-28 23:38                         ` Neil Horman
2013-07-29  0:07                         ` Ben Hutchings
2013-07-29  0:21                           ` David Miller
2013-07-29  0:26                           ` Eric Dumazet
2013-07-29  9:55                         ` Luis Henriques
2013-07-29 10:57                           ` Eric Dumazet
2013-07-29 12:09                             ` Luis Henriques
2013-07-29 15:30                               ` Eric Dumazet
2013-07-29 17:24                                 ` Eric Dumazet
2013-07-30  8:53                                   ` Luis Henriques
2013-07-31  2:11                                   ` David Miller
2013-07-31 17:48                                     ` Benjamin Poirier
2013-07-31 17:56                                       ` Eric Dumazet
2013-07-31 19:01                                       ` David Miller
2013-08-01  1:57                                         ` Eric Dumazet [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=1375322240.10515.115.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=benjamin.poirier@gmail.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=jcliburn@gmail.com \
    --cc=luis.henriques@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.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