All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/4] linux-yocto: consolidated pull request
Date: Sun, 27 Jun 2021 12:50:36 -0400	[thread overview]
Message-ID: <cover.1624811389.git.bruce.ashfield@gmail.com> (raw)

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

This is v2 of the series, my update to the latest -stable ran with
the wrong arguments and I only updated the yocto-bsp bbappend. That
of course messed up the stacking of all the following SRCREV updates.

I've recreate that 5.10-stable commit, and then restacked the rest
of the changes. Everything built fine here, but let me know if you
run into issues.

---------

v1 message:

  Here are the next -stable integrations, along with some kconfig cleanup
  and a backport of the identified rcu looking issue.
  
  Next up will be libc-headers updates, along with the 5.13 reference
  kernel (and the dropping of 5.4 from active in master).
  
  Cheers,

  Bruce


The following changes since commit 2834c2f853bd0d988dd1e35d4300005be05f8b19:

  populate_sdk_ext: copy BBMULTICONFIG files (2021-06-22 15:18:11 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (4):
  linux-yocto/5.10: update to v5.10.46
  linux-yocto/5.4: update to v5.4.128
  linux-yocto/5.10: features/nft_tables: refresh config options
  linux-yocto/5.10: rcu: Fix stall-warning deadlock due to non-release
    of rcu_node ->lock

 .../linux/linux-yocto-rt_5.10.bb              |  6 ++---
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.10.bb            |  8 +++----
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 ++++++++---------
 6 files changed, 37 insertions(+), 37 deletions(-)

-- 
2.19.1


             reply	other threads:[~2021-06-27 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 16:50 Bruce Ashfield [this message]
2021-06-27 16:50 ` [PATCH 1/4] linux-yocto/5.10: update to v5.10.46 Bruce Ashfield
2021-06-27 16:50 ` [PATCH 2/4] linux-yocto/5.4: update to v5.4.128 Bruce Ashfield
2021-06-27 16:50 ` [PATCH 3/4] linux-yocto/5.10: features/nft_tables: refresh config options Bruce Ashfield
2021-06-27 16:50 ` [PATCH 4/4] linux-yocto/5.10: rcu: Fix stall-warning deadlock due to non-release of rcu_node ->lock Bruce Ashfield

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=cover.1624811389.git.bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.