From: Ira Weiny <ira.weiny@intel.com>
To: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>,
<gregkh@linuxfoundation.org>
Cc: <outreachy@lists.linux.dev>, <martyn@welchs.me.uk>,
<manohar.vanga@gmail.com>, <zoo868e@gmail.com>,
<jerrykang026@gmail.com>, <cuigaosheng1@huawei.com>,
<arnd@arndb.de>, <linux-kernel@vger.kernel.org>,
<linux-staging@lists.linux.dev>, <eng.mennamahmoud.mm@gmail.com>
Subject: Re: [PATCH 1/2] staging: vme_user: add space around operators
Date: Wed, 15 Mar 2023 11:47:36 -0700 [thread overview]
Message-ID: <641212c8d481f_253a1e29437@iweiny-mobl.notmuch> (raw)
In-Reply-To: <b56c7b94e59a4051373af8b5d90a0685dfc9233a.1678882204.git.eng.mennamahmoud.mm@gmail.com>
Menna Mahmoud wrote:
> add a space before and after the operator, for readability.
>
> Reported By checkpatch script:
>
> CHECK: spaces preferred around that '+' (ctx:VxV)
> + image->bus_resource.name = kmalloc(VMENAMSIZ+3, GFP_ATOMIC);
> ^
> CHECK: spaces preferred around that '<<' (ctx:VxV)
> + temp_ctl &= ~(3<<4);
> ^
> CHECK: spaces preferred around that '>>' (ctx:VxV)
> + cbar = (cbar & TSI148_CRCSR_CBAR_M)>>3;
> ^
> CHECK: spaces preferred around that '<<' (ctx:VxV)
> + iowrite32be(cbar<<3, bridge->base + TSI148_CBAR);
Similar comment to what Fabio made.
But I'll add some formatting comments.
It looks like you have submitted a 2 patch series which fixes all the
checkpatch errors in the vme_user driver?
Kudos for separating out the 2 patches for the 2 different types of
checkpatch errors! And for submitting a series which fixes the entire
driver!
But you should also include a cover letter for your series.
How are you creating this series? Are you using 'git format-patch'?
'b4'? If not using 'b4' I strongly recommend it.[*]
Both of those tools can help with formatting a cover letter and b4 will
help keep track of multiple versions of the series as you fix things.
Ira
[*] https://git.kernel.org/pub/scm/utils/b4/b4.git
next prev parent reply other threads:[~2023-03-15 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 12:21 [PATCH 1/2] staging: vme_user: add space around operators Menna Mahmoud
2023-03-15 12:21 ` [PATCH 2/2] staging: vme_user: remove unnecessary blank lines Menna Mahmoud
2023-03-15 13:19 ` Fabio M. De Francesco
2023-03-15 13:24 ` Menna Mahmoud
2023-03-15 18:47 ` Ira Weiny [this message]
2023-03-15 19:14 ` [PATCH 1/2] staging: vme_user: add space around operators Menna Mahmoud
2023-03-16 0:18 ` Ira Weiny
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=641212c8d481f_253a1e29437@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=arnd@arndb.de \
--cc=cuigaosheng1@huawei.com \
--cc=eng.mennamahmoud.mm@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jerrykang026@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=outreachy@lists.linux.dev \
--cc=zoo868e@gmail.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