public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: stable-commits@vger.kernel.org, Yuezhang.Mo@sony.com,
	Namjae Jeon <linkinjeon@kernel.org>,
	Sungjong Seo <sj1557.seo@samsung.com>
Subject: Re: Patch "exfat: move exfat_entry_set_cache from heap to stack" has been added to the 5.10-stable tree
Date: Wed, 9 Aug 2023 09:33:44 +0200	[thread overview]
Message-ID: <2023080916-retype-backup-ecfd@gregkh> (raw)
In-Reply-To: <2023080949-reveal-curling-20fa@gregkh>

On Wed, Aug 09, 2023 at 09:32:18AM +0200, Greg KH wrote:
> On Tue, Aug 08, 2023 at 09:49:19PM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >     exfat: move exfat_entry_set_cache from heap to stack
> > 
> > to the 5.10-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      exfat-move-exfat_entry_set_cache-from-heap-to-stack.patch
> > and it can be found in the queue-5.10 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> This patch broke the build, so I've dropped it, and the other exfat
> patches from the 5.10.y queue for now.

I take that back, I've only dropped this one patch, the others can stay
(including the real fix that this one was added for.)  So all should be
good now.

thanks,

greg k-h

      reply	other threads:[~2023-08-09  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230809014920.320461-1-sashal@kernel.org>
2023-08-09  7:32 ` Patch "exfat: move exfat_entry_set_cache from heap to stack" has been added to the 5.10-stable tree Greg KH
2023-08-09  7:33   ` Greg KH [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=2023080916-retype-backup-ecfd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Yuezhang.Mo@sony.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj1557.seo@samsung.com \
    --cc=stable-commits@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