From: Jiri Slaby <jslaby@suse.cz>
To: Kamal Mostafa <kamal@canonical.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Zoltan Kiss <zoltan.kiss@citrix.com>,
"David S. Miller" <davem@davemloft.net>,
Ben Hutchings <ben@decadent.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kamal Mostafa <kamal.mostafa@canonical.com>
Subject: Re: [PATCH -stable 3.10 3.12 3.13] core, nfqueue, openvswitch: fix compilation warning
Date: Tue, 14 Apr 2015 10:13:50 +0200 [thread overview]
Message-ID: <552CCC3E.6000901@suse.cz> (raw)
In-Reply-To: <1428942368.5907.7.camel@sputnik-fhd>
On 04/13/2015, 06:26 PM, Kamal Mostafa wrote:
> On Mon, 2015-04-13 at 16:41 +0200, Jiri Slaby wrote:
>> Stable commit "core, nfqueue, openvswitch: Orphan frags in
>> skb_zerocopy and handle errors", upstream commit
>> 36d5fe6a000790f56039afe26834265db0a3ad4c, was not correctly backported
>> and missed to change a const 'from' parameter to non-const. This
>> results in a new batch of warnings:
>
> Just FYI, the backport in 3.13-stable[0] -- Ben Hutchings' work --
> actually does not exhibit this problem. nfqnl_zcopy() already has the
> const removed and the file yields no compile warnings.
That is quite interesting, because 3.10's version supposed to be the
Ben's 3.13 backport too, according to the commit log. Maybe a
wrong/older version was merged to 3.10 (and 3.12)?
> [0] http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=commitdiff;h=f2287ffc0e9c3d39cbc4ea9e2312640758201dfc
thanks,
--
js
suse labs
prev parent reply other threads:[~2015-04-14 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 14:41 [PATCH -stable 3.10 3.12 3.13] core, nfqueue, openvswitch: fix compilation warning Jiri Slaby
2015-04-13 16:26 ` Kamal Mostafa
2015-04-14 8:13 ` Jiri Slaby [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=552CCC3E.6000901@suse.cz \
--to=jslaby@suse.cz \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kamal.mostafa@canonical.com \
--cc=kamal@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zoltan.kiss@citrix.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).