All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Blum <blum@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Olivia Mackall <olivia@selenic.com>, Kees Cook <kees@kernel.org>,
	Michael Buesch <mb@bu3sch.de>, Andrew Morton <akpm@osdl.org>,
	Jan Beulich <jbeulich@novell.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Chris Wright <chrisw@sous-sol.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] hwrng: intel - return -ENOMEM when ioremap() fails
Date: Fri, 2 Oct 2026 10:31:56 +0200	[thread overview]
Message-ID: <ar9r_KsYh2qGSfE6@kernel.org> (raw)
In-Reply-To: <ar9bjjPC6xAgfPzT@gondor.apana.org.au>

On Fri, Oct 02, 2026 at 05:21:50PM +1000, Herbert Xu wrote:
> On Tue, Sep 22, 2026 at 08:11:01PM +0200, Thorsten Blum wrote:
> > intel_init_hw_struct() incorrectly returns -EBUSY when ioremap() fails.
> > Return -ENOMEM instead.
> > 
> > Fixes: 641dd002d207 ("[PATCH] fix Intel RNG detection")
> 
> This commit ID appears to be incorrect (but the subject is correct).

The commit ID is from stable, in mainline it is:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c24c95a085c6b52c11c2f5afecc38b0ca143cdae

The correct tag is therefore:

Fixes: c24c95a085c6 ("[PATCH] fix Intel RNG detection")

Should I submit a v2 or can you apply it like this?

Thanks,
Thorsten

      reply	other threads:[~2026-10-02  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 18:11 [PATCH 1/2] hwrng: intel - return -ENOMEM when ioremap() fails Thorsten Blum
2026-09-22 18:11 ` [PATCH 2/2] hwrng: intel - return -ENOMEM when kmalloc_obj() fails Thorsten Blum
2026-10-02  8:25   ` Herbert Xu
2026-10-02  7:21 ` [PATCH 1/2] hwrng: intel - return -ENOMEM when ioremap() fails Herbert Xu
2026-10-02  8:31   ` Thorsten Blum [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=ar9r_KsYh2qGSfE6@kernel.org \
    --to=blum@kernel.org \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=gregkh@suse.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jbeulich@novell.com \
    --cc=kees@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=olivia@selenic.com \
    /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.