From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: richard.purdie@linuxfoundation.org,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/7] linux-yocto: consolidated kernel pull request
Date: Tue, 8 Aug 2023 12:43:11 +0200 [thread overview]
Message-ID: <2023080810431190bf01b5@mail.local> (raw)
In-Reply-To: <cover.1691465503.git.bruce.ashfield@gmail.com>
Hello Bruce,
While I didn't test this series yet, as discussed, I've tried to switch
to 6.4 by default. I got this warning:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/7876/steps/13/logs/stdio
WARNING: linux-yocto-tiny-6.4.3+gitAUTOINC+dab56f52aa_dee78ad196-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:
[NOTE]: 'CONFIG_USB_HID' last val (y) and .config val (n) do not match
[INFO]: CONFIG_USB_HID : n
[INFO]: raw config text:
config USB_HID
tristate "USB HID transport layer"
default y
select HID
depends on USB && INPUT && USB && HID_SUPPORT
help
Say Y here if you want to connect USB keyboards,
mice, joysticks, graphic tablets, or any other HID based devices
to your computer via USB, as well as Uninterruptible Power Supply
(UPS) and monitor control devices.
You can't use this driver and the HIDBP (Boot Protocol) keyboard
and mouse drivers at the same time. More information is available:
<file:Documentation/input/input.rst>.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called usbhid.
Config 'USB_HID' has the following Direct dependencies (USB_HID=n):
USB(=y) && INPUT(=y) && HID_SUPPORT(=n)
Parent dependencies are:
INPUT [y] USB [y] HID_SUPPORT [n]
[INFO]: config 'CONFIG_USB_HID' was set, but it wasn't assignable, check (parent) dependencies
master has 86adbe4db668 ("linux-yocto-tiny/6.4: fix configuration
warnings (HID)") so I guess there is something missing.
On 07/08/2023 23:35:46-0400, Bruce Ashfield wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Richard,
>
> Here's my queued set of -stable updates (as well as a -dev kernel bump).
>
> I've got another round of updates under test, and will send them when
> ready.
>
> 6.4 marches along, it'll be up to date when those last issues keeping
> it from being the default are resolved.
>
> Bruce
>
> The following changes since commit 058a44165ce375f405063e73a9fcd1b2757ef8da:
>
> bitbake: fetch2: Check if path is 'None' before calculating checksums (2023-08-04 11:48:26 +0100)
>
> are available in the Git repository at:
>
> https://git.yoctoproject.org/poky-contrib zedd/kernel
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (7):
> linux-yocto/6.4: fix CONFIG_LEDS_TRIGGER_GPIO kernel audit warning
> linux-yocto/6.4: update to v6.4.6
> linux-yocto/6.1: update to v6.1.41
> linux-yocto/6.4: update to v6.4.7
> linux-yocto-dev: bump to v6.5+
> linux-yocto/6.4: update to v6.4.8
> linux-yocto/6.1: update to v6.1.43
>
> meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 +--
> .../linux/linux-yocto-rt_6.1.bb | 6 ++--
> .../linux/linux-yocto-rt_6.4.bb | 6 ++--
> .../linux/linux-yocto-tiny_6.1.bb | 6 ++--
> .../linux/linux-yocto-tiny_6.4.bb | 6 ++--
> meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +++++++++----------
> meta/recipes-kernel/linux/linux-yocto_6.4.bb | 28 +++++++++----------
> 7 files changed, 42 insertions(+), 42 deletions(-)
>
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#185630): https://lists.openembedded.org/g/openembedded-core/message/185630
> Mute This Topic: https://lists.openembedded.org/mt/100615695/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-08-08 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 3:35 [PATCH 0/7] linux-yocto: consolidated kernel pull request bruce.ashfield
2023-08-08 3:35 ` [PATCH 1/7] linux-yocto/6.4: fix CONFIG_LEDS_TRIGGER_GPIO kernel audit warning bruce.ashfield
2023-08-08 3:35 ` [PATCH 2/7] linux-yocto/6.4: update to v6.4.6 bruce.ashfield
2023-08-08 3:35 ` [PATCH 3/7] linux-yocto/6.1: update to v6.1.41 bruce.ashfield
2023-08-08 3:35 ` [PATCH 4/7] linux-yocto/6.4: update to v6.4.7 bruce.ashfield
2023-08-08 3:35 ` [PATCH 5/7] linux-yocto-dev: bump to v6.5+ bruce.ashfield
2023-08-08 3:35 ` [PATCH 6/7] linux-yocto/6.4: update to v6.4.8 bruce.ashfield
2023-08-08 3:35 ` [PATCH 7/7] linux-yocto/6.1: update to v6.1.43 bruce.ashfield
2023-08-08 10:43 ` Alexandre Belloni [this message]
2023-08-08 12:49 ` [OE-core] [PATCH 0/7] linux-yocto: consolidated kernel pull request Bruce Ashfield
[not found] ` <1779695BCF00A2D5.10230@lists.openembedded.org>
2023-08-08 17:09 ` Bruce Ashfield
2023-08-08 20:49 ` Alexandre Belloni
2023-08-09 3:36 ` Bruce Ashfield
[not found] ` <177999C4BABCB592.10230@lists.openembedded.org>
2023-08-09 12:26 ` 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=2023080810431190bf01b5@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox