From: ebiederm@xmission.com (Eric W. Biederman)
To: Jiri Slaby <jslaby@suse.cz>
Cc: David Miller <davem@davemloft.net>,
ML netdev <netdev@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
stable@vger.kernel.org
Subject: Re: v3.12-stable-queue build errors
Date: Mon, 27 Apr 2015 10:35:51 -0500 [thread overview]
Message-ID: <87fv7lk2i0.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <553DF71E.7060409@suse.cz> (Jiri Slaby's message of "Mon, 27 Apr 2015 10:45:18 +0200")
Jiri Slaby <jslaby@suse.cz> writes:
> On 04/25/2015, 04:16 PM, Guenter Roeck wrote:
>> Several powerpc build fail with:
>>
>> drivers/net/ethernet/freescale/gianfar.c: In function 'gfar_start_xmit':
>> drivers/net/ethernet/freescale/gianfar.c:2146:3: error: implicit declaration of
>> function 'dev_consume_skb_any' [-Werror=implicit-function-declaration]
>> dev_consume_skb_any(skb);
>>
>> dev_consume_skb_any() does not exist in 3.12.
>>
>> Introduced by 'gianfar: Carefully free skbs in functions called by netpoll'.
>
> Eric, David,
>
> what action should I take here?
>
> 1) take also:
> commit e6247027e5173c00efb2084d688d06ff835bc3b0
> Author: Eric Dumazet <edumazet@google.com>
> Date: Thu Dec 5 04:45:08 2013 -0800
>
> net: introduce dev_consume_skb_any()
>
>
> 2) drop 'gianfar: Carefully free skbs in functions called by netpoll'
> from stable-3.12
This is probably the most reasonable. KISS.
> 3) any other idea?
#define dev_consume_sky_any dev_kfree_skb_any
The correctness fix is updating the code to handle any context. The
consume vs kfree accouting difference is not particularly interesting.
Eric
next prev parent reply other threads:[~2015-04-27 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150425141609.GA1147@roeck-us.net>
2015-04-27 8:45 ` v3.12-stable-queue build errors Jiri Slaby
2015-04-27 15:35 ` Eric W. Biederman [this message]
2015-04-27 16:17 ` Guenter Roeck
2015-04-27 16:25 ` David Miller
2015-04-27 18:00 ` Jiri Slaby
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=87fv7lk2i0.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=jslaby@suse.cz \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=stable@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).