public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "François Valenduc" <francoisvalenduc@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.19 000/342] 6.19.11-rc1 review
Date: Fri, 3 Apr 2026 08:15:58 +0200	[thread overview]
Message-ID: <2026040323-anthology-sandlot-3bb9@gregkh> (raw)
In-Reply-To: <d39aabec-f102-4339-b72a-ee138fe0c002@gmail.com>

On Thu, Apr 02, 2026 at 09:09:38PM +0200, François Valenduc wrote:
> 
> Le 2/04/26 à 15:38, Greg Kroah-Hartman a écrit :
> > On Thu, Apr 02, 2026 at 03:19:15PM +0200, François Valenduc wrote:
> > > It seems there is no difference between the final stable versions and
> > > what was posted for review.
> > > So I guess I will have the problem in 6.18.21 and 6.19.11. I will try
> > > later today.
> > > 6.19.10 and 6.18.20 worked just fine.
> > If you can track it down to a specific commit, please let us know.
> > 
> > thanks,
> > 
> > greg k-h
> 
> In fact this has nothing to do with a kernel problem. This was caused by a
> strange change in dracut which happened at the same time and some keyboard
> layout files were not included anymore.
> I would never have noticed if I didn't need an azerty keyboard 🙂 No wonder
> that git bisect was inconclusive.
> 
> Sorry for the noise.

Hey, the number of times I've been "bitten" by the French keyboard
layout is way too many :)

Thanks for letting us know, glad it's not a kernel issue.

greg k-h

  reply	other threads:[~2026-04-03  6:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 16:17 [PATCH 6.19 000/342] 6.19.11-rc1 review Greg Kroah-Hartman
2026-03-31 17:23 ` Ronald Warsow
2026-03-31 18:24 ` Dileep malepu
2026-03-31 21:18 ` François Valenduc
2026-04-01 18:20   ` François Valenduc
     [not found]     ` <2026040220-sincere-undaunted-65b5@gregkh>
     [not found]       ` <CACU-xRtcWU=RKOfhL+8B2YmYnPN-fxc+TYc4rjaQEFc5qAk1+g@mail.gmail.com>
     [not found]         ` <2026040243-dwelled-overdrive-51b3@gregkh>
2026-04-02 19:09           ` François Valenduc
2026-04-03  6:15             ` Greg Kroah-Hartman [this message]
2026-04-02  7:56   ` Thorsten Leemhuis
2026-03-31 21:52 ` Justin Forbes
2026-03-31 22:18 ` Florian Fainelli
2026-04-01 11:42   ` Greg Kroah-Hartman
2026-04-01  6:21 ` Peter Schneider
2026-04-01  6:45 ` Shung-Hsi Yu
2026-04-01  7:28 ` Brett A C Sheffield
2026-04-01  9:17 ` Ron Economos
2026-04-01  9:19 ` Jon Hunter
2026-04-01 10:06   ` Luna Jernberg
2026-04-01 11:14 ` Takeshi Ogasawara
2026-04-01 15:58 ` Jeffrin Thalakkottoor
2026-04-01 16:09 ` Shuah Khan
2026-04-01 17:35 ` Mark Brown
2026-04-02  9:43 ` Barry K. Nathan
2026-04-02 12:04 ` Miguel Ojeda
2026-04-07 11:59 ` Pavel Machek

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=2026040323-anthology-sandlot-3bb9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=francoisvalenduc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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