From: Michal Simek <michal.simek@xilinx.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Jolly Shah <jolly.shah@xilinx.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejas Patel <tejas.patel@xilinx.com>,
linux-arm-kernel@lists.infradead.org,
Rajan Vaja <rajan.vaja@xilinx.com>
Subject: [PATCH v2 0/3] firmware: xilinx: Clean up series
Date: Wed, 2 Dec 2020 08:38:47 +0100 [thread overview]
Message-ID: <cover.1606894725.git.michal.simek@xilinx.com> (raw)
Hi,
for being able to review new changes more effectively it is good to get rid
of existing kernel-doc and checkpatch violations.
That's why this small clean up series.
Based on
https://lore.kernel.org/r/e606233d15bfdc594535dd34eb85472b42f61830.1606832997.git.michal.simek@xilinx.com
Thanks,
Michal
Changes in v2:
- keep variable name and type on the same line - reported by Joe Perches
Michal Simek (3):
firmware: xilinx: Remove additional newline
firmware: xilinx: Add a blank line after function declaration
firmware: xilinx: Properly align function parameter
include/linux/firmware/xlnx-zynqmp.h | 43 ++++++++++++++++++++++++----
1 file changed, 38 insertions(+), 5 deletions(-)
--
2.29.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-02 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 7:38 Michal Simek [this message]
2020-12-02 7:38 ` [PATCH v2 1/3] firmware: xilinx: Remove additional newline Michal Simek
2020-12-02 7:38 ` [PATCH v2 2/3] firmware: xilinx: Add a blank line after function declaration Michal Simek
2020-12-02 7:38 ` [PATCH v2 3/3] firmware: xilinx: Properly align function parameter Michal Simek
2020-12-09 14:03 ` [PATCH v2 0/3] firmware: xilinx: Clean up series Michal Simek
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=cover.1606894725.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolly.shah@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=rajan.vaja@xilinx.com \
--cc=tejas.patel@xilinx.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).