Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: linux-rdma@vger.kernel.org, Md Haris Iqbal <haris.iqbal@ionos.com>
Cc: bvanassche@acm.org, jgg@ziepe.ca, jinpu.wang@ionos.com
Subject: Re: [PATCH v2 for-next 0/9] Misc patches for RTRS
Date: Wed, 22 Nov 2023 13:44:20 +0200	[thread overview]
Message-ID: <170065346066.28148.2038477589985381532.b4-ty@kernel.org> (raw)
In-Reply-To: <20231120154146.920486-1-haris.iqbal@ionos.com>


On Mon, 20 Nov 2023 16:41:37 +0100, Md Haris Iqbal wrote:
> Please consider to include following changes to the next merge window.
> 
> Changes in V2 for all patches:
> 	Add Fixes: tag
> 
> Jack Wang (4):
>   RDMA/rtrs-srv: Do not unconditionally enable irq
>   RDMA/rtrs-clt: Start hb after path_up
>   RDMA/rtrs-clt: Fix the max_send_wr setting
>   RDMA/rtrs-clt: Remove the warnings for req in_use check
> 
> [...]

Applied, thanks!

[1/9] RDMA/rtrs-srv: Do not unconditionally enable irq
      https://git.kernel.org/rdma/rdma/c/3ee7ecd712048a
[2/9] RDMA/rtrs-clt: Start hb after path_up
      https://git.kernel.org/rdma/rdma/c/3e44a61b5db873
[3/9] RDMA/rtrs-srv: Check return values while processing info request
      https://git.kernel.org/rdma/rdma/c/ed1e52aefa16f1
[4/9] RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true
      https://git.kernel.org/rdma/rdma/c/3a71cd6ca0ce33
[5/9] RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight
      https://git.kernel.org/rdma/rdma/c/c4d32e77fc1006
[6/9] RDMA/rtrs-clt: Fix the max_send_wr setting
      https://git.kernel.org/rdma/rdma/c/6d09f6f7d7584e
[7/9] RDMA/rtrs-clt: Remove the warnings for req in_use check
      https://git.kernel.org/rdma/rdma/c/0c8bb6eb70ca41
[8/9] RDMA/rtrs-clt: use %pe to print errors
      (no commit info)
[9/9] RDMA/rtrs: use %pe to print errors
      (no commit info)

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>

      parent reply	other threads:[~2023-11-22 11:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 15:41 [PATCH v2 for-next 0/9] Misc patches for RTRS Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 1/9] RDMA/rtrs-srv: Do not unconditionally enable irq Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 2/9] RDMA/rtrs-clt: Start hb after path_up Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 3/9] RDMA/rtrs-srv: Check return values while processing info request Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 4/9] RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 5/9] RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 6/9] RDMA/rtrs-clt: Fix the max_send_wr setting Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 7/9] RDMA/rtrs-clt: Remove the warnings for req in_use check Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 8/9] RDMA/rtrs-clt: use %pe to print errors Md Haris Iqbal
2023-11-20 15:41 ` [PATCH v2 for-next 9/9] RDMA/rtrs: " Md Haris Iqbal
2023-11-22 11:44 ` Leon Romanovsky [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=170065346066.28148.2038477589985381532.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=haris.iqbal@ionos.com \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@ionos.com \
    --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