All of lore.kernel.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] kernel-yocto: consolidated pull request
Date: Tue, 22 Mar 2022 13:19:49 -0400	[thread overview]
Message-ID: <cover.1647969481.git.bruce.ashfield@gmail.com> (raw)

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

Richard,

Here are the config, -stable (and -stable -rt) updates that I've gathered
and tested over the last while.

I don't expect any major issues .. but one never fully knows. If anything
does pop up, I'm here to fix.

Cheers,

Bruce

The following changes since commit ac942fea081eaae89df2a37c72965a01d026284b:

  kernel-yocto: allow patch author date to be commit date (2022-03-21 07:39:24 -0400)

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 (10):
  linux-yocto: nohz_full boot arg fix
  linux-yocto/5.10: split vtpm for more granular inclusion
  linux-yocto/5.15: split vtpm for more granular inclusion
  linux-yocto/5.10: cfg/debug: add configs for kcsan
  linux-yocto/5.15: cfg/debug: add configs for kcsan
  linux-yocto/5.15: update to v5.15.27
  linux-yocto-rt/5.15: update to -rt34
  linux-yocto-rt/5.10: update to -rt61
  linux-yocto/5.15: update to v5.15.30
  linux-yocto/5.10: update to v5.10.107

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

-- 
2.19.1



             reply	other threads:[~2022-03-22 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 17:19 bruce.ashfield [this message]
2022-03-22 17:19 ` [PATCH 01/10] linux-yocto: nohz_full boot arg fix bruce.ashfield
2022-03-22 17:19 ` [PATCH 02/10] linux-yocto/5.10: split vtpm for more granular inclusion bruce.ashfield
2022-03-22 17:19 ` [PATCH 03/10] linux-yocto/5.15: " bruce.ashfield
2022-03-22 17:19 ` [PATCH 04/10] linux-yocto/5.10: cfg/debug: add configs for kcsan bruce.ashfield
2022-03-22 17:19 ` [PATCH 05/10] linux-yocto/5.15: " bruce.ashfield
2022-03-22 17:19 ` [PATCH 06/10] linux-yocto/5.15: update to v5.15.27 bruce.ashfield
2022-03-22 17:19 ` [PATCH 07/10] linux-yocto-rt/5.15: update to -rt34 bruce.ashfield
2022-03-22 17:19 ` [PATCH 08/10] linux-yocto-rt/5.10: update to -rt61 bruce.ashfield
2022-03-22 17:19 ` [PATCH 09/10] linux-yocto/5.15: update to v5.15.30 bruce.ashfield
2022-03-22 17:19 ` [PATCH 10/10] linux-yocto/5.10: update to v5.10.107 bruce.ashfield
  -- strict thread matches above, loose matches on Subject: below --
2024-08-01 15:08 [PATCH 00/10] kernel-yocto: consolidated pull request bruce.ashfield
2024-08-02  9:02 ` Richard Purdie
2024-08-02 11:18   ` Bruce Ashfield
2024-08-06  3:24   ` Bruce Ashfield
2024-08-06  3:56     ` Jon Mason
2020-08-12 17:03 Bruce Ashfield
2017-02-01 15:30 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.1647969481.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.