From: David Miller <davem@davemloft.net>
To: x0066660@ti.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org,
santosh.shilimkar@ti.com, Tristram.Ha@micrel.com
Subject: Re: [PATCH] KS8851: Correct RX packet allocation
Date: Wed, 08 Sep 2010 21:47:27 -0700 (PDT) [thread overview]
Message-ID: <20100908.214727.214214200.davem@davemloft.net> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A530450AB386D@dlee03.ent.ti.com>
From: "Arce, Abraham" <x0066660@ti.com>
Date: Wed, 8 Sep 2010 18:26:55 -0500
> From: Eric Dumazet <eric.dumazet@gmail.com>
>
> Use netdev_alloc_skb_ip_align() helper and do correct allocation
>
> Tested-by: Abraham Arce <x0066660@ti.com>
> Signed-off-by: Abraham Arce <x0066660@ti.com>
Applied, thank you.
prev parent reply other threads:[~2010-09-09 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 23:26 [PATCH] KS8851: Correct RX packet allocation Arce, Abraham
2010-09-09 4:47 ` David Miller [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=20100908.214727.214214200.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Tristram.Ha@micrel.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=x0066660@ti.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).