public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: stable@kernel.org, stable@vger.kernel.org, tytso@mit.edu,
	adilger.kernel@dilger.ca, boyu.mt@taobao.com,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	leejones@google.com, Ye Bin <yebin10@huawei.com>,
	syzbot+4faa160fa96bfba639f8@syzkaller.appspotmail.com,
	Jun Nie <jun.nie@linaro.org>
Subject: Re: [PATCH RESEND][for-stable 5.10, 5.4, 4.19, 4.14] ext4: fix kernel BUG in 'ext4_write_inline_data_end()'
Date: Thu, 30 Mar 2023 14:51:19 +0200	[thread overview]
Message-ID: <ZCWFx_iRPRr1Afw0@kroah.com> (raw)
In-Reply-To: <661ff1fb-ab0d-e0a3-693c-073443f556df@linaro.org>

On Thu, Mar 30, 2023 at 01:21:55PM +0100, Tudor Ambarus wrote:
> 
> 
> On 3/30/23 13:01, Greg KH wrote:
> > On Thu, Mar 30, 2023 at 12:42:27PM +0100, Tudor Ambarus wrote:
> >> + stable@vger.kernel.org
> >>
> >> Hi!
> >>
> >> Can we queue this to Linux stable, please?
> > 
> > Queue what exactly?
> > 
> 
> The patch on which we reply:
> https://lore.kernel.org/all/20230307103840.2603092-1-tudor.ambarus@linaro.org/
> 
> Shall I do something different next time?

Please resend, your commit message is very confusing and this patch is
long out of my review queue for some reason.

thanks,

greg k-h

  reply	other threads:[~2023-03-30 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230307103840.2603092-1-tudor.ambarus@linaro.org>
2023-03-30 11:42 ` [PATCH RESEND][for-stable 5.10, 5.4, 4.19, 4.14] ext4: fix kernel BUG in 'ext4_write_inline_data_end()' Tudor Ambarus
2023-03-30 12:01   ` Greg KH
2023-03-30 12:21     ` Tudor Ambarus
2023-03-30 12:51       ` Greg KH [this message]
2023-03-30 13:47         ` Tudor Ambarus

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=ZCWFx_iRPRr1Afw0@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=boyu.mt@taobao.com \
    --cc=jun.nie@linaro.org \
    --cc=leejones@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+4faa160fa96bfba639f8@syzkaller.appspotmail.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=tytso@mit.edu \
    --cc=yebin10@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox