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 09:16:35 -0800 [thread overview]
Message-ID: <20221215091635.15cde90c@hermes.local> (raw)
In-Reply-To: <MW4PR11MB57760310424E2B73F53F933CFDE19@MW4PR11MB5776.namprd11.prod.outlook.com>
On Thu, 15 Dec 2022 16:13:07 +0000
"Drewek, Wojciech" <wojciech.drewek@intel.com> wrote:
> > -----Original Message-----
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: czwartek, 15 grudnia 2022 17:00
> > To: Drewek, Wojciech <wojciech.drewek@intel.com>
> > Cc: netdev@vger.kernel.org
> > Subject: Re: Missing patch in iproute2 6.1 release
> >
> > 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.
>
> 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)?
I do merge of release from next to main during the kernel merge window.
next prev parent reply other threads:[~2022-12-15 17:16 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
2022-12-15 16:13 ` Drewek, Wojciech
2022-12-15 17:16 ` Stephen Hemminger [this message]
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=20221215091635.15cde90c@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