From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Jeff Barnes <jeffbarnes@linux.microsoft.com>
Subject: Re: [REQUEST] crypto backport for 6.6
Date: Fri, 24 Apr 2026 13:53:17 +0200 [thread overview]
Message-ID: <2026042410-corporate-voyage-34c3@gregkh> (raw)
In-Reply-To: <aetX6JwQ72GEv80e@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Fri, Apr 24, 2026 at 04:45:44AM -0700, Hamza Mahfooz wrote:
> On Fri, Apr 24, 2026 at 01:42:42PM +0200, Greg Kroah-Hartman wrote:
> > On Fri, Apr 24, 2026 at 04:35:13AM -0700, Hamza Mahfooz wrote:
> > > Hi,
> > >
> > > Please include commit 35e13e0eacf4 ("crypto: testmgr - Hide ENOENT
> > > errors better") in kernel 6.6, as it resolves a kernel panic.
> >
> > I see no such commit in Linus's tree, are you sure that is correct?
> >
> > > (you will also need commit fc0f08317135 ("crypto: testmgr - Hide ENOENT
> > > errors") to have it apply cleanly).
> >
> > I don't see that commit id either anywhere.
> >
> > What tree are you looking at?
> >
> > confused,
>
> Whoops, I was looking at my local tree, the correct commits are:
>
> 6318fbe26e67 ("crypto: testmgr - Hide ENOENT errors better")
> 4eded6d14f5b ("crypto: testmgr - Hide ENOENT errors")
That's better, now queued up :)
greg k-h
prev parent reply other threads:[~2026-04-24 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 11:35 [REQUEST] crypto backport for 6.6 Hamza Mahfooz
2026-04-24 11:42 ` Greg Kroah-Hartman
2026-04-24 11:45 ` Hamza Mahfooz
2026-04-24 11:53 ` Greg Kroah-Hartman [this message]
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=2026042410-corporate-voyage-34c3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=jeffbarnes@linux.microsoft.com \
--cc=sashal@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