From: Andre Tomt <andre@tomt.net>
To: Sasha Levin <Alexander.Levin@microsoft.com>,
Greg KH <gregkh@linuxfoundation.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [GIT PULL] commits for Linux 4.17
Date: Thu, 23 Aug 2018 03:37:24 +0200 [thread overview]
Message-ID: <2ff8aaee-d867-a397-0b00-7eb42f30d8ca@tomt.net> (raw)
In-Reply-To: <CY4PR21MB07765564188CD093CE617ADCFB240@CY4PR21MB0776.namprd21.prod.outlook.com>
On 10. aug. 2018 02:22, Sasha Levin wrote:
<snip>
> Arnaldo Carvalho de Melo (1):
> tools include uapi: Update if_link.h to pick IFLA_{BRPORT_ISOLATED,VXLAN_TTL_INHERIT}
This commit references two mainline commits:
7d850abd5f4e ("net: bridge: add support for port isolation")
72f6d71e491e ("vxlan: add ttl inherit support")
However they are first seen in 4.18-rc1, and thus makes the 4.17.x
headers out of sync:
> $ diff -u include/uapi/linux/if_link.h tools/include/uapi/linux/if_link.h
> --- include/uapi/linux/if_link.h 2018-06-03 23:15:21.000000000 +0200
> +++ tools/include/uapi/linux/if_link.h 2018-08-23 03:27:56.185758005 +0200
> @@ -333,6 +333,7 @@
> IFLA_BRPORT_BCAST_FLOOD,
> IFLA_BRPORT_GROUP_FWD_MASK,
> IFLA_BRPORT_NEIGH_SUPPRESS,
> + IFLA_BRPORT_ISOLATED,
> __IFLA_BRPORT_MAX
> };
> #define IFLA_BRPORT_MAX (__IFLA_BRPORT_MAX - 1)
> @@ -516,6 +517,7 @@
> IFLA_VXLAN_COLLECT_METADATA,
> IFLA_VXLAN_LABEL,
> IFLA_VXLAN_GPE,
> + IFLA_VXLAN_TTL_INHERIT,
> __IFLA_VXLAN_MAX
> };
> #define IFLA_VXLAN_MAX (__IFLA_VXLAN_MAX - 1)
it is
queue-4.17/tools-include-uapi-update-if_link.h-to-pick-ifla_-brport_isolated-vxlan_ttl_inherit.patch
in stable-queue.git
next prev parent reply other threads:[~2018-08-23 5:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 0:22 [GIT PULL] commits for Linux 4.17 Sasha Levin
2018-08-10 8:09 ` Greg KH
2018-08-10 13:26 ` Sasha Levin
2018-08-12 11:23 ` Greg KH
2018-08-14 18:03 ` Sasha Levin
2018-08-14 18:52 ` Greg KH
2018-08-22 7:38 ` Greg KH
2018-08-23 1:37 ` Andre Tomt [this message]
2018-08-23 7:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-07-28 1:45 Sasha Levin
2018-07-28 10:08 ` 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=2ff8aaee-d867-a397-0b00-7eb42f30d8ca@tomt.net \
--to=andre@tomt.net \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.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).