From: Leon Romanovsky <leon@kernel.org>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Cheng Xu <chengyou@linux.alibaba.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"dledford@redhat.com" <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"KaiShen@linux.alibaba.com" <KaiShen@linux.alibaba.com>,
"tonylu@linux.alibaba.com" <tonylu@linux.alibaba.com>
Subject: Re: Re: [PATCH rdma-next v2 09/11] RDMA/erdma: Add the erdma module
Date: Wed, 19 Jan 2022 13:31:01 +0200 [thread overview]
Message-ID: <Yef2daIDIf9R3IYP@unreal> (raw)
In-Reply-To: <BYAPR15MB263126902D1FC48911A42BD999599@BYAPR15MB2631.namprd15.prod.outlook.com>
On Wed, Jan 19, 2022 at 10:15:43AM +0000, Bernard Metzler wrote:
>
>
> > -----Original Message-----
> > From: Cheng Xu <chengyou@linux.alibaba.com>
> > Sent: Wednesday, 19 January 2022 05:19
> > To: Bernard Metzler <BMT@zurich.ibm.com>; jgg@ziepe.ca;
> > dledford@redhat.com
> > Cc: leon@kernel.org; linux-rdma@vger.kernel.org;
> > KaiShen@linux.alibaba.com; tonylu@linux.alibaba.com
> > Subject: [EXTERNAL] Re: [PATCH rdma-next v2 09/11] RDMA/erdma: Add the
> > erdma module
> >
> >
> >
> > On 1/18/22 8:53 PM, Bernard Metzler wrote:
> >
> > <...>
> >
> > >> +static int erdma_res_cb_init(struct erdma_dev *dev)
> > >> +{
> > >> + int i;
> > >> +
> > >> + for (i = 0; i < ERDMA_RES_CNT; i++) {
> > >> + dev->res_cb[i].next_alloc_idx = 1;
> > >> + spin_lock_init(&dev->res_cb[i].lock);
> > >> + dev->res_cb[i].bitmap = kcalloc(BITS_TO_LONGS(dev-
> > >>> res_cb[i].max_cap),
> > >> + sizeof(unsigned long), GFP_KERNEL);
> > >
> > > better stay with less than 80 chars per line
> > > throughout the patch series (I count currently 287 line wraps).
> > >
> >
> > The kernel now allows 100 chars per line, and the checkpath.pl also
> > checks using the new rule now. I will try to change this to 80 chars,
> > but it actually makes some code not friendly for reading due to
> > indent.
> >
>
> Do we have a recommendation/agreement to stay with 80 chars per line
> for the RDMA subsystem? I'd like it, but I am not sure.
Yes, we continue to use old 80 chars limit.
Thanks
>
> > <...>
> >
>
> Thanks,
> Bernard.
>
next prev parent reply other threads:[~2022-01-19 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 10:15 Re: [PATCH rdma-next v2 09/11] RDMA/erdma: Add the erdma module Bernard Metzler
2022-01-19 11:31 ` Leon Romanovsky [this message]
2022-01-20 2:51 ` Cheng Xu
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=Yef2daIDIf9R3IYP@unreal \
--to=leon@kernel.org \
--cc=BMT@zurich.ibm.com \
--cc=KaiShen@linux.alibaba.com \
--cc=chengyou@linux.alibaba.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=tonylu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).