From: Eric Biggers <ebiggers@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Sagi Grimberg <sagi@grimberg.me>,
Andrey God <andreygod83@protonmail.com>,
Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH AUTOSEL 6.3 01/67] nvme-pci: add NVME_QUIRK_BOGUS_NID for HS-SSD-FUTURE 2048G
Date: Thu, 25 May 2023 19:02:01 +0000 [thread overview]
Message-ID: <20230525190201.GA1266801@google.com> (raw)
In-Reply-To: <20230525183144.1717540-1-sashal@kernel.org>
Hi Sasha,
This feedback is on the whole 67-patch series. I'm replying to patch 1 because
this series lacks a cover letter. Please include a cover letter next time.
This series doesn't apply because the following error happens on patch 35:
Applying: tipc: add tipc_bearer_min_mtu to calculate min mtu
error: patch failed: net/tipc/bearer.h:146
error: net/tipc/bearer.h: patch does not apply
error: patch failed: net/tipc/udp_media.c:738
error: net/tipc/udp_media.c: patch does not apply
Patch failed at 0035 tipc: add tipc_bearer_min_mtu to calculate min mtu
For the base commit I tried the latest linux-6.3.y, both with and without the
latest queue-6.3 applied.
As with any kernel patch series, please make it clear what the base commit is.
Otherwise the series is unreviewable and untestable.
- Eric
next prev parent reply other threads:[~2023-05-25 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 18:30 [PATCH AUTOSEL 6.3 01/67] nvme-pci: add NVME_QUIRK_BOGUS_NID for HS-SSD-FUTURE 2048G Sasha Levin
2023-05-25 18:30 ` [PATCH AUTOSEL 6.3 02/67] nvme-pci: add quirk for missing secondary temperature thresholds Sasha Levin
2023-05-25 18:30 ` [PATCH AUTOSEL 6.3 03/67] nvme-pci: clamp max_hw_sectors based on DMA optimized limitation Sasha Levin
2023-05-25 18:31 ` [PATCH AUTOSEL 6.3 57/67] nvme-multipath: don't call blk_mark_disk_dead in nvme_mpath_remove_disk Sasha Levin
2023-05-25 18:31 ` [PATCH AUTOSEL 6.3 58/67] nvme: do not let the user delete a ctrl before a complete initialization Sasha Levin
2023-05-25 18:31 ` [PATCH AUTOSEL 6.3 66/67] nvme-pci: Add quirk for Teamgroup MP33 SSD Sasha Levin
2023-05-25 19:02 ` Eric Biggers [this message]
2023-06-01 9:52 ` [PATCH AUTOSEL 6.3 01/67] nvme-pci: add NVME_QUIRK_BOGUS_NID for HS-SSD-FUTURE 2048G Sasha Levin
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=20230525190201.GA1266801@google.com \
--to=ebiggers@kernel.org \
--cc=andreygod83@protonmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sashal@kernel.org \
--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