From: Christoph Hellwig <hch@lst.de>
To: Prabhakar Kushwaha <prabhakar.pkin@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Prabhakar Kushwaha <pkushwaha@marvell.com>,
linux-nvme@lists.infradead.org, Sagi Grimberg <sagi@grimberg.me>,
kbusch@kernel.org, axboe@fb.com, martin.belanger@dell.com,
aelior@marvell.com, Omkar Kulkarni <okulkarni@marvell.com>,
Shai Malin <smalin@marvell.com>,
malin1024@gmail.com
Subject: Re: [PATCH] nvme-tcp: Use __dev_get_by_name instead dev_get_by_name for OPT_HOST_IFACE
Date: Mon, 12 Jul 2021 07:30:27 +0200 [thread overview]
Message-ID: <20210712053027.GB8599@lst.de> (raw)
In-Reply-To: <CAJ2QiJJ8cUL2fOfuYeLqa=LOvCBRgZ3wJ=-t4t7CL-xOpS2dtw@mail.gmail.com>
On Sun, Jul 11, 2021 at 06:47:37PM +0530, Prabhakar Kushwaha wrote:
> I am not finding this patch on updated "branch nvme-5.14" having the
> latest commit 0755d3be2d9b("nvme-tcp: can't set sk_user_data without
> write_lock").
> Am I missing something? Please note, earlier it was there with commit
> ff5af4bfb6af.
>
> Issue can still be found on the nvme-5.14 branch (top of the tree).
> Are you planning to fix this problem using any other approach?
Sorry, it looks like it got lost in a rebase. I'll pick it up for
nvme-5.14 again.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-07-12 5:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 13:39 [PATCH] nvme-tcp: Use __dev_get_by_name instead dev_get_by_name for OPT_HOST_IFACE Prabhakar Kushwaha
2021-06-18 13:42 ` Christoph Hellwig
2021-06-18 19:14 ` Sagi Grimberg
2021-06-21 1:43 ` Prabhakar Kushwaha
2021-06-23 17:19 ` Belanger, Martin
2021-06-23 21:34 ` Sagi Grimberg
2021-06-24 6:35 ` Christoph Hellwig
2021-07-11 13:17 ` Prabhakar Kushwaha
2021-07-12 5:30 ` Christoph Hellwig [this message]
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=20210712053027.GB8599@lst.de \
--to=hch@lst.de \
--cc=aelior@marvell.com \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=martin.belanger@dell.com \
--cc=okulkarni@marvell.com \
--cc=pkushwaha@marvell.com \
--cc=prabhakar.pkin@gmail.com \
--cc=sagi@grimberg.me \
--cc=smalin@marvell.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.