All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Metzmacher <metze@samba.org>
Cc: 이성현 <ihopenre@gmail.com>,
	stable@vger.kernel.org, "Namjae Jeon" <linkinjeon@kernel.org>,
	linux-cifs@vger.kernel.org
Subject: Re: Backport request: ksmbd and smbdirect fixes merged in 7.4-rc
Date: Wed, 28 Oct 2026 11:14:31 +0100	[thread overview]
Message-ID: <2026102825-episode-rival-d3fa@gregkh> (raw)
In-Reply-To: <b69a61a6-47b7-40d3-9235-2c34fa0cfc29@samba.org>

On Wed, Oct 28, 2026 at 10:04:22AM +0100, Stefan Metzmacher wrote:
> Am 27.10.26 um 17:47 schrieb 이성현:
> > On Tue, Oct 27, 2026 at 11:44PM, Greg KH wrote:
> > > Why no tag?  What happened to prevent that?
> > 
> > For 3) that is on me. When I sent ef85bad39cf2 on 2026-10-15 the
> > commit it fixes, 25e414db7033, was only in 7.3-rc, so I assumed there
> > was no released kernel to backport to and left the tag off. 7.3 was
> > then released with the bug before the fix reached mainline, which is
> > why I am asking now.
> > 
> > For 1) and 2) I am the reporter, not the author, so I cannot say why
> > the tags were not added. Namjae and Stefan are on Cc and can answer
> > that. I only noticed the gap when I checked which of the fixes had
> > reached a stable tree.
> 
> Sorry, I thought that a Fixes: tag would be enough to have commits being backported
> as needed.
> 
> I read Documentation/process/stable-kernel-rules.rst again
> and will also add stable in addition.

great, thanks!

  reply	other threads:[~2026-10-28 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 16:07 Backport request: ksmbd and smbdirect fixes merged in 7.4-rc 이성현
2026-10-27 16:44 ` Greg KH
2026-10-27 16:47   ` 이성현
2026-10-28  9:04     ` Stefan Metzmacher
2026-10-28 10:14       ` Greg KH [this message]
2026-10-29 18:43 ` Sasha Levin

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=2026102825-episode-rival-d3fa@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ihopenre@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=metze@samba.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 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.