From: Michal Simek <michal.simek@xilinx.com>
To: Philipp Zabel <p.zabel@pengutronix.de>, <linux-kernel@vger.kernel.org>
Cc: Michal Simek <michal.simek@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] reset: zynqmp: replace spaces with tabs
Date: Thu, 4 Mar 2021 17:03:20 +0100 [thread overview]
Message-ID: <b5310ccf-2004-b047-c545-cceca3b1ee64@xilinx.com> (raw)
In-Reply-To: <20210304160042.15316-1-p.zabel@pengutronix.de>
On 3/4/21 5:00 PM, Philipp Zabel wrote:
> Fixes checkpatch issues:
>
> ERROR: code indent should use tabs where possible
> #86: FILE: drivers/reset/reset-zynqmp.c:86:
> + .reset_id = 0,$
>
> WARNING: please, no spaces at the start of a line
> #86: FILE: drivers/reset/reset-zynqmp.c:86:
> + .reset_id = 0,$
>
> ERROR: code indent should use tabs where possible
> #87: FILE: drivers/reset/reset-zynqmp.c:87:
> + .num_resets = VERSAL_NR_RESETS,$
>
> WARNING: please, no spaces at the start of a line
> #87: FILE: drivers/reset/reset-zynqmp.c:87:
> + .num_resets = VERSAL_NR_RESETS,$
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> drivers/reset/reset-zynqmp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/reset/reset-zynqmp.c b/drivers/reset/reset-zynqmp.c
> index ebd433fa09dd..daa425e74c96 100644
> --- a/drivers/reset/reset-zynqmp.c
> +++ b/drivers/reset/reset-zynqmp.c
> @@ -83,8 +83,8 @@ static const struct zynqmp_reset_soc_data zynqmp_reset_data = {
> };
>
> static const struct zynqmp_reset_soc_data versal_reset_data = {
> - .reset_id = 0,
> - .num_resets = VERSAL_NR_RESETS,
> + .reset_id = 0,
> + .num_resets = VERSAL_NR_RESETS,
> };
>
> static const struct reset_control_ops zynqmp_reset_ops = {
>
Reviewed-by: Michal Simek <michal.simek@xilinx.com>
Thanks,
Michal
next prev parent reply other threads:[~2021-03-04 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 16:00 Philipp Zabel
2021-03-04 16:03 ` Michal Simek [this message]
2021-03-05 9:31 ` Philipp Zabel
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=b5310ccf-2004-b047-c545-cceca3b1ee64@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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®