From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tabot Kevin <tabot.kevin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixed coding style issues raised by checkpatch.
Date: Fri, 09 Oct 2020 17:20:41 -0700 [thread overview]
Message-ID: <a3b81f8a3b4e30c57de8528b6674fac0e57e5e4a.camel@perches.com> (raw)
In-Reply-To: <20201009081840.GB401030@kroah.com>
On Fri, 2020-10-09 at 10:18 +0200, Greg Kroah-Hartman wrote:
> On Fri, Oct 09, 2020 at 09:00:38AM +0100, Tabot Kevin wrote:
> > This patch fixes the following:
> > - Made sure alignment matched open parenthesis.
> >
> > Signed-off-by: Tabot Kevin <tabot.kevin@gmail.com>
> > ---
> > drivers/staging/greybus/audio_module.c | 8 ++++----
>
> As my bot asked you to, please use scripts/get_maintainer.pl to
> determine who, and what mailing lists, to send patches to.
fyi Tabot, he means you to use:
$ ./scripts/get_maintainer.pl -f drivers/staging/greybus/audio_module.c
Vaibhav Agarwal <vaibhav.sr@gmail.com> (maintainer:GREYBUS AUDIO PROTOCOLS DRIVERS)
Mark Greer <mgreer@animalcreek.com> (maintainer:GREYBUS AUDIO PROTOCOLS DRIVERS)
Johan Hovold <johan@kernel.org> (maintainer:GREYBUS SUBSYSTEM)
Alex Elder <elder@kernel.org> (maintainer:GREYBUS SUBSYSTEM)
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (maintainer:GREYBUS SUBSYSTEM)
greybus-dev@lists.linaro.org (moderated list:GREYBUS SUBSYSTEM)
devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
> Also, I think this patch has been rejected many times in the past,
> please check the archives first before sending it again.
Doubtful about that as almost the entire file uses
alignment to open parenthesis.
prev parent reply other threads:[~2020-10-10 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 8:00 Tabot Kevin
2020-10-09 8:18 ` Greg Kroah-Hartman
2020-10-10 0:20 ` Joe Perches [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=a3b81f8a3b4e30c57de8528b6674fac0e57e5e4a.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tabot.kevin@gmail.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
all inboxes | Powered by JetHome®