All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: yocto@lists.yoctoproject.org
Subject: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Wed,  4 Mar 2020 09:56:38 -0500	[thread overview]
Message-ID: <cover.1583333447.git.bruce.ashfield@gmail.com> (raw)

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

Hi all,

As mentioned on the technical call yesterday, here's my latest set of
5.2 updates, 5.4 updates and more importantly, the removal of 5.2 from
master.

As usual, I'll continue to support and update 5.2, just without sending
SRCREV updates to master. The last set of updates to v5.2 put it in
good shape, and they are ready for backport to any stable branches.

I ran this through the AB and didn't see any issues or old references
to v5.2.

I'll follow up to other lists to drop a few of the old bbappends.

Cheers,

Bruce


The following changes since commit 92e172b5b4de8927d36409386dfce0fc2718f5d1:

  systemd: Fix service file for race issues (2020-03-03 13:06:29 +0000)

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.2: backport perf build fix for latest binutils
  linux-yocto: common-pc-drivers.cfg: add CONFIG_INPUT_UINPUT
  linux-yocto/5.4: update to v5.4.23
  linux-yocto: drop 5.2 recipes

 .../linux/linux-yocto-rt_5.2.bb               | 44 ---------------
 .../linux/linux-yocto-rt_5.4.bb               |  6 +--
 .../linux/linux-yocto-tiny_5.2.bb             | 32 -----------
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +--
 meta/recipes-kernel/linux/linux-yocto_5.2.bb  | 54 -------------------
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 ++++----
 6 files changed, 18 insertions(+), 148 deletions(-)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.2.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.2.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_5.2.bb

-- 
2.19.1


WARNING: multiple messages have this Message-ID (diff)
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Wed,  4 Mar 2020 09:55:20 -0500	[thread overview]
Message-ID: <cover.1583333447.git.bruce.ashfield@gmail.com> (raw)

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

Hi all,

As mentioned on the technical call yesterday, here's my latest set of
5.2 updates, 5.4 updates and more importantly, the removal of 5.2 from
master.

As usual, I'll continue to support and update 5.2, just without sending
SRCREV updates to master. The last set of updates to v5.2 put it in
good shape, and they are ready for backport to any stable branches.

I ran this through the AB and didn't see any issues or old references
to v5.2.

I'll follow up to other lists to drop a few of the old bbappends.

Cheers,

Bruce


The following changes since commit 92e172b5b4de8927d36409386dfce0fc2718f5d1:

  systemd: Fix service file for race issues (2020-03-03 13:06:29 +0000)

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.2: backport perf build fix for latest binutils
  linux-yocto: common-pc-drivers.cfg: add CONFIG_INPUT_UINPUT
  linux-yocto/5.4: update to v5.4.23
  linux-yocto: drop 5.2 recipes

 .../linux/linux-yocto-rt_5.2.bb               | 44 ---------------
 .../linux/linux-yocto-rt_5.4.bb               |  6 +--
 .../linux/linux-yocto-tiny_5.2.bb             | 32 -----------
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +--
 meta/recipes-kernel/linux/linux-yocto_5.2.bb  | 54 -------------------
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 ++++----
 6 files changed, 18 insertions(+), 148 deletions(-)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.2.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.2.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_5.2.bb

-- 
2.19.1



             reply	other threads:[~2020-03-04 14:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 14:55 bruce.ashfield [this message]
2020-03-04 14:56 ` [PATCH 0/4] kernel-yocto: consolidated pull request Bruce Ashfield
2020-03-04 14:55 ` [PATCH 1/4] linux-yocto/5.2: backport perf build fix for latest binutils bruce.ashfield
2020-03-04 14:55 ` [PATCH 2/4] linux-yocto: common-pc-drivers.cfg: add CONFIG_INPUT_UINPUT bruce.ashfield
2020-03-04 14:55 ` [PATCH 3/4] linux-yocto/5.4: update to v5.4.23 bruce.ashfield
2020-03-04 14:55 ` [PATCH 4/4] linux-yocto: drop 5.2 recipes bruce.ashfield
2020-03-04 14:57 ` [PATCH 0/4] kernel-yocto: consolidated pull request Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2020-08-03 12:30 Bruce Ashfield
2019-12-30  3:07 bruce.ashfield
2016-12-02 21:09 Bruce Ashfield
2016-12-06 19:32 ` Trevor Woerner
2015-03-02 21:36 Bruce Ashfield
2013-05-31  3:28 Bruce Ashfield
2013-05-31  6:14 ` Saul Wold
2013-05-31  7:07   ` Richard Purdie
2013-05-31 12:29     ` 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.1583333447.git.bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@lists.yoctoproject.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.