From: Joel Stanley <joel@jms.id.au>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Linux kernel updates and v6.0
Date: Thu, 6 Oct 2022 01:26:13 +0000 [thread overview]
Message-ID: <CACPK8XfrECvJtwZ8AR1EgsVHpSnkKCVp2LovCXCyFXBpjeBbfQ@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XdERea0Mt+3o1z2TwbN_NXJ-FDYf8mxUEAWe5Lp7oFRmg@mail.gmail.com>
On Wed, 28 Sept 2022 at 06:34, Joel Stanley <joel@jms.id.au> wrote:
for this work.
> I have prepared a v6.0 tree that contains backports of the FSI and
> Aspeed v6.1 patches, and a small set of existing patches. I will
> publish this on Monday, or once v6.0 final has been tagged.
This slipped as we had a public holiday on Monday, and there were a
few yocto issues to sort out before I could get the tree through CI.
I've now pushed dev-6.0 to openbmc/linux.
The +1 party is here:
https://gerrit.openbmc.org/c/openbmc/openbmc/+/57706
Please join in.
> As promised the last time we rebased, the Nuvoton patches that have
> not seen any updates since they were merged in 2019 have been dropped.
> They are welcome to be resubmitted as long as they are also being
> worked on upstream.
Tomer has been working with me to get the recent Nuvoton work
backported to 6.0. There remains a chunk of work that hasn't been
posted to the upstream lists and therefore isn't in the openbmc tree
yet. I encourage those who maintain systems with a npcm7xx and npcm8xx
to help there.
> Please address any future patches to the dev-6.0 tree.
If you have pending patches then please let me know that you want them
merged to the dev-6.0 branch. Otherwise, rebase and re-send them to
the list.
Cheers,
Joel
next prev parent reply other threads:[~2022-10-06 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:34 Linux kernel updates and v6.0 Joel Stanley
2022-09-28 22:30 ` William Kennington
2022-10-05 11:32 ` Patrick Williams
2022-10-24 4:32 ` Joel Stanley
2022-10-06 1:26 ` Joel Stanley [this message]
2022-10-06 3:31 ` Patrick Williams
2022-10-06 8:33 ` Joel Stanley
2022-10-06 7:04 ` Quan Nguyen
2022-10-06 8:37 ` Joel Stanley
2022-10-06 12:52 ` Quan Nguyen
2022-10-24 0:07 ` Tao Ren
2022-10-24 4:31 ` Joel Stanley
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=CACPK8XfrECvJtwZ8AR1EgsVHpSnkKCVp2LovCXCyFXBpjeBbfQ@mail.gmail.com \
--to=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.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).