[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW4PR11MB57760310424E2B73F53F933CFDE19@MW4PR11MB5776.namprd11.prod.outlook.com>
Date: Thu, 15 Dec 2022 16:13:07 +0000
From: "Drewek, Wojciech" <wojciech.drewek@...el.com>
To: Stephen Hemminger <stephen@...workplumber.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Missing patch in iproute2 6.1 release
> -----Original Message-----
> From: Stephen Hemminger <stephen@...workplumber.org>
> Sent: czwartek, 15 grudnia 2022 17:00
> To: Drewek, Wojciech <wojciech.drewek@...el.com>
> Cc: netdev@...r.kernel.org
> Subject: Re: Missing patch in iproute2 6.1 release
>
> On Thu, 15 Dec 2022 10:28:16 +0000
> "Drewek, Wojciech" <wojciech.drewek@...el.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.
Merge windows for iproute2 are sync to kernel windows?
I should sent this patch before merge window for 6.1 was closed (I sent it after it was closed)?
Powered by blists - more mailing lists