From: Christoph Hellwig <firstname.lastname@example.org> To: Sasha Levin <email@example.com> Cc: Sagi Grimberg <firstname.lastname@example.org>, Marta Rybczynska <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org>, Charles Machalow <email@example.com>, linux-kernel <firstname.lastname@example.org>, linux-nvme <email@example.com>, axboe <firstname.lastname@example.org>, email@example.com, kbusch <firstname.lastname@example.org>, Christoph Hellwig <email@example.com> Subject: Re: [PATCH] nvme: change nvme_passthru_cmd64 to explicitly mark rsvd Date: Wed, 6 Nov 2019 02:09:40 +0100 [thread overview] Message-ID: <20191106010940.GA3474@lst.de> (raw) In-Reply-To: <20191106000836.GH4787@sasha-vm> On Tue, Nov 05, 2019 at 07:08:36PM -0500, Sasha Levin wrote: > On Tue, Nov 05, 2019 at 04:31:44PM +0100, Christoph Hellwig wrote: >> On Tue, Nov 05, 2019 at 08:39:12AM +0100, Marta Rybczynska wrote: >>> Looks good to me. However, please note that the new ioctl made it already to 5.3.8. >> >> It wasn't in 5.3, but it seems like you are right and it somehow got >> picked for the stable releases. >> >> Sasha, can you please revert 76d609da9ed1cc0dc780e2b539d7b827ce28f182 >> in 5.3-stable ASAP and make sure crap like backporting new ABIs that >> haven't seen a release yet is never ever going to happen again? > > Sure, I'll revert it. I guess I wasn't expecting to see something like > this in a -rc release. How did it make it into one if it's not a fix? 76d609da9ed1cc0dc780e2b539d7b827ce28f182 is a backport of 65e68edce0db433aa0c2b26d7dc14fbbbeb89fbb, which went into 5.4-rc2 and was not marked for stable. It might kinda bend the normal merge window rules a little, but I don't see how it could be considered something to backport. _______________________________________________ Linux-nvme mailing list Linuxfirstname.lastname@example.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-11-06 1:09 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-05 6:15 Charles Machalow 2019-11-05 7:39 ` Marta Rybczynska 2019-11-05 15:31 ` Christoph Hellwig 2019-11-06 0:08 ` Sasha Levin 2019-11-06 0:18 ` Keith Busch 2019-11-06 1:09 ` Christoph Hellwig [this message] 2019-11-05 14:34 ` Christoph Hellwig 2019-11-05 15:26 ` Keith Busch 2019-11-05 20:56 ` Charles Machalow 2019-11-05 21:21 ` Keith Busch
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=20191106010940.GA3474@lst.de \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] nvme: change nvme_passthru_cmd64 to explicitly mark rsvd' \ /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
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 NNTP newsgroup(s).