From: Konstantin Taranov <kotaranov@microsoft.com>
To: Leon Romanovsky <leon@kernel.org>,
Konstantin Taranov <kotaranov@linux.microsoft.com>
Cc: Wei Hu <weh@microsoft.com>,
"sharmaajay@microsoft.com" <sharmaajay@microsoft.com>,
Long Li <longli@microsoft.com>, "jgg@ziepe.ca" <jgg@ziepe.ca>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH rdma-next v2 1/1] RDMA/mana_ib: process QP error events in mana_ib
Date: Mon, 10 Jun 2024 07:21:00 +0000 [thread overview]
Message-ID: <DB9PR83MB0537451CDAA082BA24BC5723B4C62@DB9PR83MB0537.EURPRD83.prod.outlook.com> (raw)
In-Reply-To: <20240609104618.GC8976@unreal>
> Please run checkpatch.pl on your patches before sending them. I fixed it and
> applied.
Thanks, Leon! I completely forgot to re-check. It will not happen again.
>
> ➜ kernel git:(wip/leon-for-next) mkt ci
> 878a8e752041 (HEAD -> build) RDMA/mana_ib: process QP error events in
> mana_ib
> WARNING: line length of 88 exceeds 80 columns
> #133: FILE: drivers/infiniband/hw/mana/mana_ib.h:340:
> +static inline struct mana_ib_qp *mana_get_qp_ref(struct mana_ib_dev
> +*mdev, uint32_t qid)
>
> WARNING: line length of 82 exceeds 80 columns
> #167: FILE: drivers/infiniband/hw/mana/qp.c:405:
> + return xa_insert_irq(&mdev->qp_table_wq, qp->ibqp.qp_num, qp,
> + GFP_KERNEL);
>
> WARNING: line length of 81 exceeds 80 columns
> #170: FILE: drivers/infiniband/hw/mana/qp.c:408:
> +static void mana_table_remove_qp(struct mana_ib_dev *mdev, struct
> +mana_ib_qp *qp)
>
> Thanks
next prev parent reply other threads:[~2024-06-10 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 10:08 Konstantin Taranov
2024-06-09 10:46 ` Leon Romanovsky
2024-06-10 7:21 ` Konstantin Taranov [this message]
2024-06-09 10:46 ` Leon Romanovsky
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=DB9PR83MB0537451CDAA082BA24BC5723B4C62@DB9PR83MB0537.EURPRD83.prod.outlook.com \
--to=kotaranov@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kotaranov@linux.microsoft.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=sharmaajay@microsoft.com \
--cc=weh@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®