From: Leon Romanovsky <leon@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 0/4] RDMA/srp: Handle dev_set_name() failure
Date: Sun, 28 Aug 2022 13:04:39 +0300 [thread overview]
Message-ID: <Yws9t6Xj/08izIdR@unreal> (raw)
In-Reply-To: <20220825213900.864587-1-bvanassche@acm.org>
On Thu, Aug 25, 2022 at 02:38:56PM -0700, Bart Van Assche wrote:
> Hi Jason,
>
> This patch series includes one patch that handles dev_set_name() failure and
> three refactoring patches. Please consider these patches for the next merge
> window.
You confuse me. "next merge window" means that patches are targeted to
-next, but you added stable@... tag and didn't add any Fixes lines.
I applied everything to rdma-next and removed stable@ tag.
Thanks
>
> Thanks,
>
> Bart.
>
> Bart Van Assche (4):
> RDMA/srp: Rework the srp_add_port() error path
> RDMA/srp: Remove the srp_host.released completion
> RDMA/srp: Handle dev_set_name() failure
> RDMA/srp: Use the attribute group mechanism for sysfs attributes
>
> drivers/infiniband/ulp/srp/ib_srp.c | 50 +++++++++++++++--------------
> drivers/infiniband/ulp/srp/ib_srp.h | 1 -
> 2 files changed, 26 insertions(+), 25 deletions(-)
>
next prev parent reply other threads:[~2022-08-28 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 21:38 [PATCH 0/4] RDMA/srp: Handle dev_set_name() failure Bart Van Assche
2022-08-25 21:38 ` [PATCH 1/4] RDMA/srp: Rework the srp_add_port() error path Bart Van Assche
2022-08-25 21:38 ` [PATCH 2/4] RDMA/srp: Remove the srp_host.released completion Bart Van Assche
2022-08-25 21:38 ` [PATCH 3/4] RDMA/srp: Handle dev_set_name() failure Bart Van Assche
2022-08-25 21:39 ` [PATCH 4/4] RDMA/srp: Use the attribute group mechanism for sysfs attributes Bart Van Assche
2022-08-28 10:04 ` Leon Romanovsky [this message]
2022-08-28 19:50 ` [PATCH 0/4] RDMA/srp: Handle dev_set_name() failure Bart Van Assche
2022-08-29 5:41 ` Leon Romanovsky
2022-08-30 18:10 ` Jason Gunthorpe
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=Yws9t6Xj/08izIdR@unreal \
--to=leon@kernel.org \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@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