All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Moving kernel to Linux 5.2
Date: Wed, 10 Jul 2019 09:46:04 +0000	[thread overview]
Message-ID: <CACPK8XfLruW7RN+6G=eAjuY_pKPRbTVBs8aueJs==6QzmhDY2w@mail.gmail.com> (raw)

It's that time again. I've pushed a dev-5.2 branch to openbmc/linux
that contains the patches from dev-5.1 rebased on top of v5.2.

The bump is in this commit:

 https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/23344

Note that there's a systemd-network bug exposed by this change so you
will need this commit to do any testing (or work around the issue by
manually bringing up the device):

 https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/23412

Please test, +1 and report your results.

Where possible I've cherry picked the patches that will land in 5.3.
This includes the device tree patches, dps310, aspeed-video, and fsi
fixes.

We have 100 out of tree patches at this point in time. Of these, 58
are staged in 5.3, leaving 42 out of tree patches. The out of tree
patches include:

 - aspeed spi-nor
 - npcm clk, bpc, mailbox, ethernet, flash
 - npcm device trees
 - peci framework, associated various drivers
 - misc other patches

If you have code in the tree then please keep working on getting it upstream.

Cheers,

Joel

             reply	other threads:[~2019-07-10  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  9:46 Joel Stanley [this message]
2019-07-13  0:51 ` Moving kernel to Linux 5.2 Tao Ren

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='CACPK8XfLruW7RN+6G=eAjuY_pKPRbTVBs8aueJs==6QzmhDY2w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.