linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Laurence de Bruxelles <lfdebrux@gmail.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	 Daniel Thompson <daniel.thompson@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] backlight: corgi: Fix gpio numbers for backlight controls
Date: Thu, 30 Jun 2022 13:06:54 +0200	[thread overview]
Message-ID: <CACRpkdZhtw9ixH2oRkK7N7wWih5_0Z5FZYcMQehx8qBFBiWpaA@mail.gmail.com> (raw)
In-Reply-To: <CAKxgj33Ktnx2NxkV1BzePa+PDrkt7E25THSpRLLWVopbdb8PMg@mail.gmail.com>

On Thu, Jun 30, 2022 at 12:26 PM Laurence de Bruxelles
<lfdebrux@gmail.com> wrote:
>
> On Thu, 30 Jun 2022 at 07:53, Lee Jones <lee.jones@linaro.org> wrote:
> >
> > On Thu, 30 Jun 2022, Laurence de Bruxelles wrote:
> >
> > > > Looks correct, my mistakes (nothing to test on, that's why...)
> > > > Thanks a lot for fixing this!
> > > > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> > >
> > > No worries!
> > >
> > > > I would just send the patch directly to the SoC tree for fixes.
> > >
> > > Ah, sorry, I'm new to Linux kernel development, not sure of the
> > > correct way to do things. I sent this patch email to the list suggested
> > > by scripts/get_maintainer.pl, is there another way to send fixes to the
> > > SoC tree?
> >
> > You did?  Something must have gone wrong somewhere:
> >
> > $ ./scripts/get_maintainer.pl -f arch/arm/mach-pxa/spitz.c
> > Daniel Mack <daniel@zonque.org> (maintainer:PXA2xx/PXA3xx SUPPORT)
> > Haojian Zhuang <haojian.zhuang@gmail.com> (maintainer:PXA2xx/PXA3xx SUPPORT)
> > Robert Jarzmik <robert.jarzmik@free.fr> (maintainer:PXA2xx/PXA3xx SUPPORT)
> > Russell King <linux@armlinux.org.uk> (odd fixer:ARM PORT)
> > linux-arm-kernel@lists.infradead.org (moderated list:PXA2xx/PXA3xx SUPPORT)
> > linux-kernel@vger.kernel.org (open list)
> >
>
> I get something slightly different when I run the script.
>
> I think because the commit description has a 'Fixes' line in it.
>
> $ ./scripts/get_maintainer.pl
> 0001-backlight-corgi-Fix-gpio-numbers-for-backlight-contr.patch
> Daniel Mack <daniel@zonque.org> (maintainer:PXA2xx/PXA3xx SUPPORT)
> Haojian Zhuang <haojian.zhuang@gmail.com> (maintainer:PXA2xx/PXA3xx SUPPORT)
> Robert Jarzmik <robert.jarzmik@free.fr> (maintainer:PXA2xx/PXA3xx
> SUPPORT,blamed_fixes:1/1=100%)
> Russell King <linux@armlinux.org.uk> (odd fixer:ARM PORT)
> Daniel Thompson <daniel.thompson@linaro.org> (blamed_fixes:1/1=100%)
> Lee Jones <lee.jones@linaro.org> (blamed_fixes:1/1=100%)
> Linus Walleij <linus.walleij@linaro.org> (blamed_fixes:1/1=100%)
> linux-arm-kernel@lists.infradead.org (moderated list:PXA2xx/PXA3xx SUPPORT)
> linux-kernel@vger.kernel.org (open list)

The CC list is fine, but it's missing the SoC mail address which is
what actually get it queued. It's one of these things you just have to know
because we don't want to spam that address with random reviews, just
with finished patches to be merged.

When you are finished with the patch, send it to soc@kernel.org
simply. Then it will appear here:
https://patchwork.kernel.org/project/linux-soc/list/

Yours,
Linus Walleij

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-30 11:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 21:20 [PATCH] backlight: corgi: Fix gpio numbers for backlight controls Laurence de Bruxelles
2022-06-26 23:51 ` Linus Walleij
2022-06-30  6:38   ` Laurence de Bruxelles
2022-06-30  6:53     ` Lee Jones
2022-06-30 10:26       ` Laurence de Bruxelles
2022-06-30 11:06         ` Linus Walleij [this message]
2022-07-02  7:56           ` Laurence de Bruxelles
2022-06-27  7:43 ` Lee Jones
2022-06-30  6:41   ` Laurence de Bruxelles
2022-06-30  6:51     ` Lee Jones
2022-07-04 13:08 ` Arnd Bergmann
2022-07-04 22:04   ` Laurence de Bruxelles
2022-07-05  9:49     ` Arnd Bergmann

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=CACRpkdZhtw9ixH2oRkK7N7wWih5_0Z5FZYcMQehx8qBFBiWpaA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=lfdebrux@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robert.jarzmik@free.fr \
    /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).