From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org
Cc: Izabela Bakollari <izabela.bakollari@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wfx: Spacing and alignment cleanup
Date: Mon, 12 Oct 2020 11:16:28 +0200 [thread overview]
Message-ID: <17610782.Z3s6dbGlRe@pc-42> (raw)
In-Reply-To: <20201012082630.275118-1-izabela.bakollari@gmail.com>
On Monday 12 October 2020 10:26:30 CEST izabela.bakollari@gmail.com wrote:
> From: Izabela Bakollari <izabela.bakollari@gmail.com>
>
> This patch fixes minor issue with spacing and alignment.
>
> checkpatch message:
> CHECK: Alignment should match open parenthesis
>
> Signed-off-by: Izabela Bakollari <izabela.bakollari@gmail.com>
> ---
> drivers/staging/wfx/debug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wfx/debug.c b/drivers/staging/wfx/debug.c
> index 3f1712b7c919..83ccbab50899 100644
> --- a/drivers/staging/wfx/debug.c
> +++ b/drivers/staging/wfx/debug.c
> @@ -32,7 +32,7 @@ static const struct trace_print_flags wfx_reg_print_map[] = {
> };
>
> static const char *get_symbol(unsigned long val,
> - const struct trace_print_flags *symbol_array)
> + const struct trace_print_flags *symbol_array)
> {
> int i;
>
> --
> 2.18.4
>
Hello Izabela,
Thank you for your contribution.
This issue has already been fixed in commit d61c0848100c ("staging: wfx:
clear alignment style issues").
For your next contribution, ensure your patch applies on the last
development tree.
To get the development tree to use, you can run:
./scripts/get_maintainer.pl --scm -f drivers/staging/wfx/debug.c
--
Jérôme Pouiller
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2020-10-12 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 8:26 [PATCH] staging: wfx: Spacing and alignment cleanup izabela.bakollari
2020-10-12 9:16 ` Jérôme Pouiller [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=17610782.Z3s6dbGlRe@pc-42 \
--to=jerome.pouiller@silabs.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=izabela.bakollari@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).