From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: openbmc <openbmc@lists.ozlabs.org>,
Cosmo Chou <chou.cosmo@gmail.com>,
Eddie James <eajames@linux.ibm.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
Leo Yang <Leo-Yang@quantatw.com>,
Peter Yin <peteryin.openbmc@gmail.com>,
"tomer.maimon" <tomer.maimon@nuvoton.com>,
Matt Johnston <matt@codeconstruct.com.au>,
Tan Siewert <tan@siewert.io>
Subject: Re: openbmc/linux dev-6.18
Date: Wed, 17 Dec 2025 21:39:02 +1030 [thread overview]
Message-ID: <7537d63b15688f2d747a4f51569b67c73b23d455.camel@codeconstruct.com.au> (raw)
In-Reply-To: <0d0b4c80905c331d55043b048863c15e416cf4a4.camel@codeconstruct.com.au>
On Wed, 2025-12-17 at 21:20 +1030, Andrew Jeffery wrote:
> Hi Tomer,
>
> On Wed, 2025-12-17 at 12:43 +0200, Tomer Maimon wrote:
> > Hi Andrew,
> >
> > Thank you very much for pushing dev-6.18 to the OpenBMC Linux kernel
> > repository!
>
> No problems :)
>
> >
> > Do you have an estimate for when the dev-6.18 branch might become the
> > default branch for the OpenBMC Linux kernel?
>
> The serious answer is "when we've got consensus from the regular people
> that it's a good idea".
>
> Though if those people are quick perhaps we could hit merge as a
> holiday celebration.
As an early indication, all changes in the Gerrit topic for the fixes
and recipe bumps have passed CI.
Andrew
prev parent reply other threads:[~2025-12-17 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 10:09 openbmc/linux dev-6.18 Andrew Jeffery
2025-12-17 10:43 ` Tomer Maimon
2025-12-17 10:50 ` Andrew Jeffery
2025-12-17 11:09 ` Andrew Jeffery [this message]
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=7537d63b15688f2d747a4f51569b67c73b23d455.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Leo-Yang@quantatw.com \
--cc=chou.cosmo@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=jk@codeconstruct.com.au \
--cc=matt@codeconstruct.com.au \
--cc=openbmc@lists.ozlabs.org \
--cc=peteryin.openbmc@gmail.com \
--cc=tan@siewert.io \
--cc=tmaimon77@gmail.com \
--cc=tomer.maimon@nuvoton.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