All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bhatnagar, Rishabh" <risbhat@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "hch@lst.de" <hch@lst.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"axboe@fb.com" <axboe@fb.com>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	"Bacco, Mike" <mbacco@amazon.com>,
	"Herrenschmidt, Benjamin" <benh@amazon.com>,
	"Park, SeongJae" <sjpark@amazon.com>
Subject: Re: [PATCH v2] nvme-pci: Set min align mask before calculating max_hw_sectors
Date: Tue, 11 Oct 2022 13:35:11 -0700	[thread overview]
Message-ID: <bc7b08f4-673d-538f-e053-4edf899b9d60@amazon.com> (raw)
In-Reply-To: <Y0W09tcGK/1ZAhQh@kroah.com>


On 10/11/22 11:24 AM, Greg KH wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> On Tue, Oct 11, 2022 at 10:05:38AM -0700, Bhatnagar, Rishabh wrote:
>> On 10/10/22 11:08 PM, hch@lst.de wrote:
>>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>>>
>>>
>>>
>>> The patch already made it to Linux 6.0, so I'm not sure what we need
>>> to review again.
>> Oh, I never got any email that this was being picked up so sent it again.
>> Anyways thanks for taking it.
>> We need this patch for 5.10/5.15 stable kernels as well. I can send backport
>> patches to stable tree
>> maintainers unless there is a way for you to mark it so that its
>> automatically picked for stable trees.
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read:
>      https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> </formletter>

Since the original patch doesn't contain the CC:stable@vger.kernel.org, 
using option 2
makes sense as there is no special handling required to apply this for 
5.10/5.15.



      reply	other threads:[~2022-10-11 20:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 18:22 [PATCH v2] nvme-pci: Set min align mask before calculating max_hw_sectors Rishabh Bhatnagar
     [not found] ` <EB43F4D1-BFD0-408B-93E7-10643B59F766@amazon.com>
2022-10-10 17:55   ` Bhatnagar, Rishabh
2022-10-11  6:08     ` hch
2022-10-11 17:05       ` Bhatnagar, Rishabh
2022-10-11 18:24         ` Greg KH
2022-10-11 20:35           ` Bhatnagar, Rishabh [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=bc7b08f4-673d-538f-e053-4edf899b9d60@amazon.com \
    --to=risbhat@amazon.com \
    --cc=axboe@fb.com \
    --cc=benh@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mbacco@amazon.com \
    --cc=sagi@grimberg.me \
    --cc=sjpark@amazon.com \
    --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.