Backports Archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Revanth Rajashekar <revanth.rajashekar@intel.com>,
	linux-nvme@lists.infradead.org, hch@lst.de
Cc: kbusch@kernel.org, damien.lemoal@wdc.com, backports@vger.kernel.org
Subject: Re: [PATCH 0/3] [backport] nvme: Consolidate chunk_sectors settings
Date: Mon, 21 Sep 2020 21:25:08 +0200	[thread overview]
Message-ID: <f3b8ef76decf5b3204463f8a2267ba456562f691.camel@sipsolutions.net> (raw)
In-Reply-To: <20200921184728.11291-1-revanth.rajashekar@intel.com> (sfid-20200921_204456_447027_687C7A95)

On Mon, 2020-09-21 at 12:47 -0600, Revanth Rajashekar wrote:
> Backport commit 38adf94e166e3cb4eb89683458ca578051e8218d and it's
> dependencies to linux-stable 5.4.y.
> 

backports@vger.kernel.org isn't for backporting kernel patches...

I guess you want to CC stable if they need to pick up any of this, or
perhaps something else, but almost certainly not backports@.

johannes

--
To unsubscribe from this list: send the line "unsubscribe backports" in

      parent reply	other threads:[~2020-09-21 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 18:47 [PATCH 0/3] [backport] nvme: Consolidate chunk_sectors settings Revanth Rajashekar
2020-09-21 18:47 ` [PATCH 1/3] [backport] nvme: Cleanup and rename nvme_block_nr() Revanth Rajashekar
2020-09-21 18:47 ` [PATCH 2/3] [backport] nvme: Introduce nvme_lba_to_sect() Revanth Rajashekar
2020-09-21 18:47 ` [PATCH 3/3] [backport] nvme: consolidate chunk_sectors settings Revanth Rajashekar
2020-09-21 19:25 ` Johannes Berg [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=f3b8ef76decf5b3204463f8a2267ba456562f691.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=damien.lemoal@wdc.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=revanth.rajashekar@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).