From: Mark Greer <mgreer@animalcreek.com>
To: Jorge Eduardo Fermino Oliveia Silva <jorge.ubermensch@gmail.com>
Cc: mgreer@animalcreek.com, greybus-dev@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Header line: Coding style fix
Date: Fri, 17 Dec 2021 16:34:08 -0700 [thread overview]
Message-ID: <20211217233408.GA47062@animalcreek.com> (raw)
In-Reply-To: <20211217143408.10313-1-jorgeubermensch@gmail.com>
On Fri, Dec 17, 2021 at 11:34:08AM -0300, Jorge Eduardo Fermino Oliveia Silva wrote:
[Note: I am traveling for the next week so I won't be very responsive.]
Hi Jorge.
Before we get to the platch please remember that you should send all
Greybus patches to greybus-dev@lists.linaro.org and
linux-kernel@vger.kernel.org. I will add them in now and leave all of
the context so other can see what you sent.
> Solve CHECK: Lines should not end with a '('
>
> Reported-by: Jorge Eduardo Fermino Oliveia Silva <jorgeubermensch@gmail.com>
> Signed-off-by: Jorge Eduardo Fermino Oliveia Silva <jorgeubermensch@gmail.com>
> ---
> drivers/staging/greybus/audio_manager_private.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/greybus/audio_manager_private.h b/drivers/staging/greybus/audio_manager_private.h
> index 2b3a766c7de7..a17f09a19014 100644
> --- a/drivers/staging/greybus/audio_manager_private.h
> +++ b/drivers/staging/greybus/audio_manager_private.h
> @@ -12,10 +12,10 @@
>
> #include "audio_manager.h"
>
> -int gb_audio_manager_module_create(
> - struct gb_audio_manager_module **module,
> - struct kset *manager_kset,
> - int id, struct gb_audio_manager_module_descriptor *desc);
> +int gb_audio_manager_module_create(struct gb_audio_manager_module **module,
> + struct kset *manager_kset,
> + int id,
> + struct gb_audio_manager_module_descriptor *desc);
>
> /* module destroyed via kobject_put */
The part you're removing has all of the parameters at the same
indentation level and what you adding has them at two different
indentation levels so I'm not sure this is a step forward. Since the
kernel coding style doesn't address this specific case, AFAICS, I would
leave it as is despite the complaint. If others disagree then go ahead
as I really don't care much either way.
Mark
--
next parent reply other threads:[~2021-12-17 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Jorgecommit>
[not found] ` <20211217143408.10313-1-jorgeubermensch@gmail.com>
2021-12-17 23:34 ` Mark Greer [this message]
2021-12-20 14:57 ` [greybus-dev] " Alex Elder
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=20211217233408.GA47062@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=greybus-dev@lists.linaro.org \
--cc=jorge.ubermensch@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
all inboxes | Powered by JetHome®