From: chenweilong <chenweilong@huawei•com>
To: David Miller <davem@davemloft•net>
Cc: <netdev@vger•kernel.org>
Subject: Re: [PATCH 3.4-stable] ipv6: reallocate addrconf router for ipv6 address when lo, device up
Date: Wed, 6 Aug 2014 16:01:30 +0800 [thread overview]
Message-ID: <53E1E0DA.9070308@huawei.com> (raw)
In-Reply-To: <20140724.210839.866750629795894870.davem@davemloft.net>
Sorry.
I'll change it.
On 2014/7/25 12:08, David Miller wrote:
> From: chenweilong <chenweilong@huawei•com>
> Date: Thu, 19 Jun 2014 08:50:33 +0800
>
>> Please queue this for 3.4 stable kernel.
> ...
>> + dst_release(sp_ifa->rt);
>
> dst_release() does not take a "struct rt6_info *", and therefore
> the compile warns when you try to compile this.
>
> For something like -stable, we should be as conservative as possible,
> I expect at a minimum that you look at the build for warnings added by
> your change.
>
>
next prev parent reply other threads:[~2014-08-06 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 0:50 [PATCH 3.4-stable] ipv6: reallocate addrconf router for ipv6 address when lo, device up chenweilong
2014-07-25 4:08 ` David Miller
2014-08-06 8:01 ` chenweilong [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-09 1:35 chenweilong
2014-06-17 10:23 chenweilong
2014-08-05 18:18 ` Greg KH
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=53E1E0DA.9070308@huawei.com \
--to=chenweilong@huawei$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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