LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Daniel Wagner <dwagner@suse.de>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>,
yi.he@emc.com
Subject: Re: [PATCH] nvme-tcp: Do not reset transport on data digest errors
Date: Mon, 23 Aug 2021 10:13:49 -0700 [thread overview]
Message-ID: <3ffb2ff9-0074-7f3e-6c40-18837c0a02d7@grimberg.me> (raw)
In-Reply-To: <20210818124430.hokmfa25lnhxnswu@carbon.lan>
>>> It is the correct place, lets see that it doesn't increase the struct.
>>
>> It should not according pahole:
>
> Anything I need to do to get this patch accepted?
Yes, move the status to nvme_tcp_request, I think its
a more appropriate place for it.
next prev parent reply other threads:[~2021-08-23 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 12:15 Daniel Wagner
2021-08-06 19:42 ` Sagi Grimberg
2021-08-09 9:09 ` Daniel Wagner
2021-08-11 1:02 ` Sagi Grimberg
2021-08-11 10:31 ` Daniel Wagner
2021-08-18 12:44 ` Daniel Wagner
2021-08-23 17:13 ` Sagi Grimberg [this message]
2021-08-20 10:20 ` Hannes Reinecke
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=3ffb2ff9-0074-7f3e-6c40-18837c0a02d7@grimberg.me \
--to=sagi@grimberg.me \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=yi.he@emc.com \
--subject='Re: [PATCH] nvme-tcp: Do not reset transport on data digest errors' \
/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).