All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@mellanox.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Shlomo Pongratz <shlomop@mellanox.com>,
	Erez Shitrit <erezsh@mellanox.com>
Subject: Re: getting warn once around skb_try_coalesce
Date: Tue, 10 Jul 2012 15:19:36 +0300	[thread overview]
Message-ID: <4FFC1DD8.80103@mellanox.com> (raw)
In-Reply-To: <1341919328.3265.4871.camel@edumazet-glaptop>

On 7/10/2012 2:22 PM, Eric Dumazet wrote:
> And of course we also can fix the truesize bug. (Not sure it will fix 
> the warning, but worth trying) 



thanks, we will give that a try and let you know

  reply	other threads:[~2012-07-10 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10  9:54 getting warn once around skb_try_coalesce Or Gerlitz
2012-07-10 10:18 ` Eric Dumazet
2012-07-10 11:14   ` Eric Dumazet
2012-07-10 11:22     ` Eric Dumazet
2012-07-10 12:19       ` Or Gerlitz [this message]
2012-07-10 12:35       ` Shlomo Pongartz
2012-07-10 13:01         ` Eric Dumazet

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=4FFC1DD8.80103@mellanox.com \
    --to=ogerlitz@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=erezsh@mellanox.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shlomop@mellanox.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 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.