From: Stephen Hemminger <stephen@networkplumber.org>
To: "Drewek, Wojciech" <wojciech.drewek@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Missing patch in iproute2 6.1 release
Date: Thu, 15 Dec 2022 07:59:43 -0800 [thread overview]
Message-ID: <20221215075943.3f51def8@hermes.local> (raw)
In-Reply-To: <MW4PR11MB5776DC6756FF5CB106F3ED26FDE19@MW4PR11MB5776.namprd11.prod.outlook.com>
On Thu, 15 Dec 2022 10:28:16 +0000
"Drewek, Wojciech" <wojciech.drewek@intel.com> wrote:
> Hi Stephen,
>
> I've seen iproute2 6.1 being released recently[1] and I'm wondering why my patch[2] was included.
> Is there anything wrong with the patch?
>
> Regards,
> Wojtek
>
> [1] https://lore.kernel.org/netdev/20221214082705.5d2c2e7f@hermes.local/
> [2] https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=9313ba541f793dd1600ea4bb7c4f739accac3e84
Iproute2 next tree holds the patches for the next release.
That patch went into the next tree after 6.1 was started.
It will get picked up when next is merged to main.
next prev parent reply other threads:[~2022-12-15 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 10:28 Missing patch in iproute2 6.1 release Drewek, Wojciech
2022-12-15 15:59 ` Stephen Hemminger [this message]
2022-12-15 16:13 ` Drewek, Wojciech
2022-12-15 17:16 ` Stephen Hemminger
2022-12-15 17:21 ` Drewek, Wojciech
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=20221215075943.3f51def8@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=wojciech.drewek@intel.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