From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Franziska Naepelt <franziska.naepelt@gmail.com>,
Ladislav Michl <oss-lists@triops.cz>
Subject: Re: [PATCH v2] mips: Fix spacing issue
Date: Fri, 9 Jun 2023 10:21:25 +0200 [thread overview]
Message-ID: <20230609082125.GD8160@alpha.franken.de> (raw)
In-Reply-To: <20230530065949.22247-1-franziska.naepelt@gmail.com>
On Tue, May 30, 2023 at 08:59:49AM +0200, Franziska Naepelt wrote:
> Fix some indentation issues and remove the following checkpatch issue:
> - ERROR: need consistent spacing around '-' (ctx:WxV)
>
> Co-Developed-by: Ladislav Michl <oss-lists@triops.cz>
> Signed-off-by: Franziska Naepelt <franziska.naepelt@gmail.com>
> ---
> v2:
> - Apply review remarks
>
> arch/mips/sibyte/swarm/platform.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/arch/mips/sibyte/swarm/platform.c b/arch/mips/sibyte/swarm/platform.c
> index 484969db7713..339d77a0a08f 100644
> --- a/arch/mips/sibyte/swarm/platform.c
> +++ b/arch/mips/sibyte/swarm/platform.c
> @@ -88,15 +88,15 @@ device_initcall(swarm_pata_init);
> #define sb1250_dev_struct(num) \
> static struct resource sb1250_res##num = { \
> .name = "SB1250 MAC " __stringify(num), \
> - .flags = IORESOURCE_MEM, \
> - .start = A_MAC_CHANNEL_BASE(num), \
> - .end = A_MAC_CHANNEL_BASE(num + 1) -1, \
> + .flags = IORESOURCE_MEM, \
> + .start = A_MAC_CHANNEL_BASE(num), \
> + .end = A_MAC_CHANNEL_BASE(num + 1) - 1, \
> };\
> static struct platform_device sb1250_dev##num = { \
> - .name = "sb1250-mac", \
> - .id = num, \
> - .resource = &sb1250_res##num, \
> - .num_resources = 1, \
> + .name = "sb1250-mac", \
> + .id = num, \
> + .resource = &sb1250_res##num, \
> + .num_resources = 1, \
> }
>
> sb1250_dev_struct(0);
>
> base-commit: 7877cb91f1081754a1487c144d85dc0d2e2e7fc4
> --
> 2.39.2 (Apple Git-143)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-06-09 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 6:59 [PATCH v2] mips: Fix spacing issue Franziska Naepelt
2023-06-09 8:21 ` Thomas Bogendoerfer [this message]
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=20230609082125.GD8160@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=franziska.naepelt@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=oss-lists@triops.cz \
/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).