From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 1/2] nvme: remove workarounds for gcc bug wrt unnamed fields in initializers
Date: Thu, 18 Jun 2020 17:32:05 +0000 [thread overview]
Message-ID: <20200618173205.GA1068826@localhost.localdomain> (raw)
In-Reply-To: <20200618171124.tfowb2ejv3bnvxr4@beryllium.lan>
On Thu, Jun 18, 2020 at 07:11:24PM +0200, Daniel Wagner wrote:
> On Thu, Jun 18, 2020 at 04:32:40PM +0200, Niklas Cassel wrote:
> > If, for some reason, we want to allow builds with gcc < 4.6.0
> > even though the minimum gcc version is now 4.8.0,
>
> Just one thing to watch out: the stable trees are still using
> older version of gcc. Note sure how relevant this is though.
While the AUTOSEL can be a bit annoying when autoselecting patches
to backport that you didn't intend, I think that it in most cases
backports fixes that has a Fixes-tag, which this doesn't.
Kind regards,
Niklas
next prev parent reply other threads:[~2020-06-18 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 14:32 [PATCH 1/2] nvme: remove workarounds for gcc bug wrt unnamed fields in initializers Niklas Cassel
2020-06-18 14:32 ` [PATCH 2/2] nvmet: " Niklas Cassel
2020-06-18 15:23 ` Chaitanya Kulkarni
2020-06-18 16:15 ` Niklas Cassel
2020-06-18 17:29 ` Chaitanya Kulkarni
2020-06-18 20:00 ` Niklas Cassel
2020-06-18 18:42 ` kernel test robot
2020-06-19 2:34 ` kernel test robot
2020-06-18 17:11 ` [PATCH 1/2] nvme: " Daniel Wagner
2020-06-18 17:32 ` Niklas Cassel [this message]
2020-06-18 17:48 ` kernel test robot
2020-06-19 1:26 ` kernel test robot
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=20200618173205.GA1068826@localhost.localdomain \
--to=niklas.cassel@wdc.com \
--cc=axboe@fb.com \
--cc=dwagner@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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