From: David Miller <davem@davemloft.net>
To: chunkeey@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v3] net: emac: remove IBM_EMAC_RX_SKB_HEADROOM
Date: Wed, 06 Feb 2019 20:16:36 -0800 (PST) [thread overview]
Message-ID: <20190206.201636.1952666229057488227.davem@davemloft.net> (raw)
In-Reply-To: <20190205212009.8820-1-chunkeey@gmail.com>
From: Christian Lamparter <chunkeey@gmail.com>
Date: Tue, 5 Feb 2019 22:20:09 +0100
> The EMAC driver had a custom IBM_EMAC_RX_SKB_HEADROOM
> Kconfig option that reserved additional skb headroom for RX.
> This patch removes the option and migrates the code
> to use napi_alloc_skb() and netdev_alloc_skb_ip_align()
> in its place.
>
> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
> ---
> v2 -> v3: drop inlines
Applied to net-next.
prev parent reply other threads:[~2019-02-07 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 21:20 [PATCH v3] net: emac: remove IBM_EMAC_RX_SKB_HEADROOM Christian Lamparter
2019-02-07 4:16 ` 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=20190206.201636.1952666229057488227.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chunkeey@gmail.com \
--cc=netdev@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 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).