From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Cc: linux@roeck-us.net, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH net-next] staging: octeon: fix build failure with XFRM enabled
Date: Sat, 22 Dec 2018 11:35:20 +0300 [thread overview]
Message-ID: <973d7244-7864-f0ff-0fe3-0061b6dffa56@cogentembedded.com> (raw)
In-Reply-To: <20181221205726.2924-1-fw@strlen.de>
Hello!
On 21.12.2018 23:57, Florian Westphal wrote:
> skb->sp doesn't exist anymore in the next-next tree, so mips defconfig
It's net-next. :-)
> no longer builds. Use helper instead to reset the secpath.
>
> Not even compile tested.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Fixes: 4165079ba328d ("net: switch secpath to use skb extension infrastructure")
> Signed-off-by: Florian Westphal <fw@strlen.de>
[...]
MBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux@roeck-us.net
Subject: Re: [PATCH net-next] staging: octeon: fix build failure with XFRM enabled
Date: Sat, 22 Dec 2018 11:35:20 +0300 [thread overview]
Message-ID: <973d7244-7864-f0ff-0fe3-0061b6dffa56@cogentembedded.com> (raw)
In-Reply-To: <20181221205726.2924-1-fw@strlen.de>
Hello!
On 21.12.2018 23:57, Florian Westphal wrote:
> skb->sp doesn't exist anymore in the next-next tree, so mips defconfig
It's net-next. :-)
> no longer builds. Use helper instead to reset the secpath.
>
> Not even compile tested.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Fixes: 4165079ba328d ("net: switch secpath to use skb extension infrastructure")
> Signed-off-by: Florian Westphal <fw@strlen.de>
[...]
MBR, Sergei
next prev parent reply other threads:[~2018-12-22 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 20:57 [PATCH net-next] staging: octeon: fix build failure with XFRM enabled Florian Westphal
2018-12-22 8:35 ` Sergei Shtylyov [this message]
2018-12-22 8:35 ` Sergei Shtylyov
2018-12-24 17:58 ` David Miller
2018-12-24 17:58 ` David Miller
2018-12-21 23:27 Guenter Roeck
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=973d7244-7864-f0ff-0fe3-0061b6dffa56@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devel@driverdev.osuosl.org \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.