From: Sasha Levin <sashal@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Gal Pressman <galpress@amazon.com>,
Shadi Ammouri <sammouri@amazon.com>,
Yossi Leybovich <sleybo@amazon.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.8 55/62] RDMA/efa: Add EFA 0xefa1 PCI ID
Date: Fri, 21 Aug 2020 15:53:22 -0400 [thread overview]
Message-ID: <20200821195322.GC8670@sasha-vm> (raw)
In-Reply-To: <20200821194036.GB2811093@nvidia.com>
On Fri, Aug 21, 2020 at 04:40:36PM -0300, Jason Gunthorpe wrote:
>On Fri, Aug 21, 2020 at 12:14:16PM -0400, Sasha Levin wrote:
>> From: Gal Pressman <galpress@amazon.com>
>>
>> [ Upstream commit d4f9cb5c5b224dca3ff752c1bb854250bf114944 ]
>>
>> Add support for 0xefa1 devices.
>>
>> Link: https://lore.kernel.org/r/20200722140312.3651-5-galpress@amazon.com
>> Reviewed-by: Shadi Ammouri <sammouri@amazon.com>
>> Reviewed-by: Yossi Leybovich <sleybo@amazon.com>
>> Signed-off-by: Gal Pressman <galpress@amazon.com>
>> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>> drivers/infiniband/hw/efa/efa_main.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>
>Wait, what? Why is this being autosel'd?
Stable trees try to pick up device enablement patches (such as patches
that add PCI IDs). I suppose that AUTOSEL get pretty eager to grab
those.
>This needs to be the last patch in a series enabling support for this
>chip, it will badly break this driver to pick it out of sequence!!
I'll drop it, thanks for letting me know!
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-08-21 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200821161423.347071-1-sashal@kernel.org>
2020-08-21 16:14 ` [PATCH AUTOSEL 5.8 55/62] RDMA/efa: Add EFA 0xefa1 PCI ID Sasha Levin
2020-08-21 19:40 ` Jason Gunthorpe
2020-08-21 19:53 ` Sasha Levin [this message]
2020-08-21 20:19 ` Jason Gunthorpe
2020-08-21 20:34 ` Sasha Levin
2020-08-23 6:43 ` Gal Pressman
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=20200821195322.GC8670@sasha-vm \
--to=sashal@kernel.org \
--cc=galpress@amazon.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sammouri@amazon.com \
--cc=sleybo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox