* who to send first patch to
@ 2018-02-15 17:32 Dafna Hirschfeld
[not found] ` <20180215173939.GA371@shraddha>
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Dafna Hirschfeld @ 2018-02-15 17:32 UTC (permalink / raw)
To: outreachy-kernel
[-- Attachment #1.1: Type: text/plain, Size: 371 bytes --]
Hi,
I follow the first-patch <https://kernelnewbies.org/Outreachyfirstpatch>
tutorial.
When running the get_maintainer.sh script, I get Greg Kroah-Hartman
<gregkh@linuxfoundation.org>.
Should I send the patch to this mailing list and add the maintainer as a
CC, or should I send two separate mails, one to this mailing list and one
to the maintainer ?
Thanks,
Dafna
[-- Attachment #1.2: Type: text/html, Size: 470 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Fwd: [Outreachy kernel] who to send first patch to
[not found] ` <20180215173939.GA371@shraddha>
@ 2018-02-15 17:40 ` Shraddha Barke
0 siblings, 0 replies; 9+ messages in thread
From: Shraddha Barke @ 2018-02-15 17:40 UTC (permalink / raw)
To: outreachy-kernel, Dafna Hirschfeld
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Thu, Feb 15, 2018 at 09:32:11AM -0800, Dafna Hirschfeld wrote:
> Hi,
> I follow the first-patch <https://kernelnewbies.org/Outreachyfirstpatch>
> tutorial.
> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>.
> Should I send the patch to this mailing list and add the maintainer as a
> CC, or should I send two separate mails, one to this mailing list and one
> to the maintainer ?
Hello Dafna :)
Welcome to the application process! You should send the patch to the
Outreachy mailing list and the relevant maintainers in a single email.
No need for separate emails.
-Shraddha
>
> Thanks,
> Dafna
>
> --
> You received this message because you are subscribed to the Google Groups
"outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
msgid/outreachy-kernel/a8ea6283-061c-4172-a7c1-e2a7e99d46f3%40googlegroups.
com.
> For more options, visit https://groups.google.com/d/optout.
--
Shraddha
[-- Attachment #2: Type: text/html, Size: 2286 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 17:32 who to send first patch to Dafna Hirschfeld
[not found] ` <20180215173939.GA371@shraddha>
@ 2018-02-15 17:42 ` Ezequiel Garcia
2018-02-15 17:48 ` Ezequiel Garcia
2018-02-15 17:46 ` Greg KH
2 siblings, 1 reply; 9+ messages in thread
From: Ezequiel Garcia @ 2018-02-15 17:42 UTC (permalink / raw)
To: Dafna Hirschfeld; +Cc: outreachy-kernel
On 15 February 2018 at 14:32, Dafna Hirschfeld <dafna3@gmail.com> wrote:
> Hi,
> I follow the first-patch tutorial.
> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>.
> Should I send the patch to this mailing list and add the maintainer as a CC,
> or should I send two separate mails, one to this mailing list and one to the
> maintainer ?
>
Just like Shraddha said, you sould send just *one* mail.
You can Cc as much developers as you want, but you'll usually want to keep
the Cc list short, Ccing only the relevant maintainers.
Let's work with an example. I just crafted a small patch removing an unused
header from arch/arm/mach-mv78xx0/common.c:
commit 42dc417bb0c0547a926880494ac3f79829bd3035 (HEAD -> orion-nand)
Author: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Date: Thu Feb 15 14:39:09 2018 -0300
ARM: mv78xx0: remove unused header
This file doesn't setup an orion-nand device, and so
it does not need the orion-nand header.
Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
diff --git a/arch/arm/mach-mv78xx0/common.c b/arch/arm/mach-mv78xx0/common.c
index f72e1e9f5fc5..89c95e365e90 100644
--- a/arch/arm/mach-mv78xx0/common.c
+++ b/arch/arm/mach-mv78xx0/common.c
@@ -19,7 +19,6 @@
#include <asm/mach/map.h>
#include <asm/mach/time.h>
#include <linux/platform_data/usb-ehci-orion.h>
-#include <linux/platform_data/mtd-orion_nand.h>
#include <plat/time.h>
#include <plat/common.h>
#include <plat/addr-map.h>
> Thanks,
> Dafna
>
> --
> You received this message because you are subscribed to the Google Groups
> "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/outreachy-kernel/a8ea6283-061c-4172-a7c1-e2a7e99d46f3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 17:32 who to send first patch to Dafna Hirschfeld
[not found] ` <20180215173939.GA371@shraddha>
2018-02-15 17:42 ` Ezequiel Garcia
@ 2018-02-15 17:46 ` Greg KH
2 siblings, 0 replies; 9+ messages in thread
From: Greg KH @ 2018-02-15 17:46 UTC (permalink / raw)
To: Dafna Hirschfeld; +Cc: outreachy-kernel
On Thu, Feb 15, 2018 at 09:32:11AM -0800, Dafna Hirschfeld wrote:
> Hi,
> I follow the first-patch <https://kernelnewbies.org/Outreachyfirstpatch>
> tutorial.
> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>.
That's it? Just me?
> Should I send the patch to this mailing list and add the maintainer as a
> CC, or should I send two separate mails, one to this mailing list and one
> to the maintainer ?
Put the maintainer(s) on the To: line, and the mailing list on the cc:
line.
Hope this helps,
greg k-h
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 17:42 ` Ezequiel Garcia
@ 2018-02-15 17:48 ` Ezequiel Garcia
2018-02-15 17:57 ` Greg KH
2018-02-15 19:58 ` Julia Lawall
0 siblings, 2 replies; 9+ messages in thread
From: Ezequiel Garcia @ 2018-02-15 17:48 UTC (permalink / raw)
To: Dafna Hirschfeld; +Cc: outreachy-kernel
On 15 February 2018 at 14:42, Ezequiel Garcia
<ezequiel@vanguardiasur.com.ar> wrote:
> On 15 February 2018 at 14:32, Dafna Hirschfeld <dafna3@gmail.com> wrote:
>> Hi,
>> I follow the first-patch tutorial.
>> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
>> <gregkh@linuxfoundation.org>.
>> Should I send the patch to this mailing list and add the maintainer as a CC,
>> or should I send two separate mails, one to this mailing list and one to the
>> maintainer ?
>>
>
> Just like Shraddha said, you sould send just *one* mail.
>
> You can Cc as much developers as you want, but you'll usually want to keep
> the Cc list short, Ccing only the relevant maintainers.
>
> Let's work with an example. I just crafted a small patch removing an unused
> header from arch/arm/mach-mv78xx0/common.c:
>
> commit 42dc417bb0c0547a926880494ac3f79829bd3035 (HEAD -> orion-nand)
> Author: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> Date: Thu Feb 15 14:39:09 2018 -0300
>
> ARM: mv78xx0: remove unused header
>
> This file doesn't setup an orion-nand device, and so
> it does not need the orion-nand header.
>
> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
>
> diff --git a/arch/arm/mach-mv78xx0/common.c b/arch/arm/mach-mv78xx0/common.c
> index f72e1e9f5fc5..89c95e365e90 100644
> --- a/arch/arm/mach-mv78xx0/common.c
> +++ b/arch/arm/mach-mv78xx0/common.c
> @@ -19,7 +19,6 @@
> #include <asm/mach/map.h>
> #include <asm/mach/time.h>
> #include <linux/platform_data/usb-ehci-orion.h>
> -#include <linux/platform_data/mtd-orion_nand.h>
> #include <plat/time.h>
> #include <plat/common.h>
> #include <plat/addr-map.h>
>
Oops... sent the mail by mistake. So, like I was saying: I have that
patch ready.
Now I need to see who I'll sent to:
./scripts/get_maintainer.pl 0001-ARM-mv78xx0-remove-unused-header.patch
Jason Cooper <jason@lakedaemon.net> (maintainer:ARM/Marvell
Dove/MV78xx0/Orion SOC support)
Andrew Lunn <andrew@lunn.ch> (maintainer:ARM/Marvell
Dove/MV78xx0/Orion SOC support)
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
(maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
Gregory Clement <gregory.clement@free-electrons.com>
(maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
Russell King <linux@armlinux.org.uk> (maintainer:ARM PORT)
linux-arm-kernel@lists.infradead.org (moderated list:ARM SUB-ARCHITECTURES)
linux-kernel@vger.kernel.org (open list)
OK, that's a long list. I'll send the patch to just the SOC
maintainers and the ARM mailing list, not all of them listed above.
git send-email --to jason@lakedaemon.net --to andrew@lunn.ch --to
sebastian.hesselbarth@gmail.com --to
gregory.clement@free-electrons.com
0001-ARM-mv78xx0-remove-unused-header.patch --cc
linux-arm-kernel@lists.infradead.org
In your case, you'll most likely pick Cc the outreachy mailing list
and send it to Greg KH (as Greg just said).
Hope it helps,
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 17:48 ` Ezequiel Garcia
@ 2018-02-15 17:57 ` Greg KH
2018-02-15 19:59 ` Julia Lawall
2018-02-15 19:58 ` Julia Lawall
1 sibling, 1 reply; 9+ messages in thread
From: Greg KH @ 2018-02-15 17:57 UTC (permalink / raw)
To: Ezequiel Garcia; +Cc: Dafna Hirschfeld, outreachy-kernel
On Thu, Feb 15, 2018 at 02:48:30PM -0300, Ezequiel Garcia wrote:
> On 15 February 2018 at 14:42, Ezequiel Garcia
> <ezequiel@vanguardiasur.com.ar> wrote:
> > On 15 February 2018 at 14:32, Dafna Hirschfeld <dafna3@gmail.com> wrote:
> >> Hi,
> >> I follow the first-patch tutorial.
> >> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> >> <gregkh@linuxfoundation.org>.
> >> Should I send the patch to this mailing list and add the maintainer as a CC,
> >> or should I send two separate mails, one to this mailing list and one to the
> >> maintainer ?
> >>
> >
> > Just like Shraddha said, you sould send just *one* mail.
> >
> > You can Cc as much developers as you want, but you'll usually want to keep
> > the Cc list short, Ccing only the relevant maintainers.
> >
> > Let's work with an example. I just crafted a small patch removing an unused
> > header from arch/arm/mach-mv78xx0/common.c:
> >
> > commit 42dc417bb0c0547a926880494ac3f79829bd3035 (HEAD -> orion-nand)
> > Author: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > Date: Thu Feb 15 14:39:09 2018 -0300
> >
> > ARM: mv78xx0: remove unused header
> >
> > This file doesn't setup an orion-nand device, and so
> > it does not need the orion-nand header.
> >
> > Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> >
> > diff --git a/arch/arm/mach-mv78xx0/common.c b/arch/arm/mach-mv78xx0/common.c
> > index f72e1e9f5fc5..89c95e365e90 100644
> > --- a/arch/arm/mach-mv78xx0/common.c
> > +++ b/arch/arm/mach-mv78xx0/common.c
> > @@ -19,7 +19,6 @@
> > #include <asm/mach/map.h>
> > #include <asm/mach/time.h>
> > #include <linux/platform_data/usb-ehci-orion.h>
> > -#include <linux/platform_data/mtd-orion_nand.h>
> > #include <plat/time.h>
> > #include <plat/common.h>
> > #include <plat/addr-map.h>
> >
>
> Oops... sent the mail by mistake. So, like I was saying: I have that
> patch ready.
> Now I need to see who I'll sent to:
>
> ./scripts/get_maintainer.pl 0001-ARM-mv78xx0-remove-unused-header.patch
> Jason Cooper <jason@lakedaemon.net> (maintainer:ARM/Marvell
> Dove/MV78xx0/Orion SOC support)
> Andrew Lunn <andrew@lunn.ch> (maintainer:ARM/Marvell
> Dove/MV78xx0/Orion SOC support)
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> Gregory Clement <gregory.clement@free-electrons.com>
> (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> Russell King <linux@armlinux.org.uk> (maintainer:ARM PORT)
> linux-arm-kernel@lists.infradead.org (moderated list:ARM SUB-ARCHITECTURES)
> linux-kernel@vger.kernel.org (open list)
>
> OK, that's a long list. I'll send the patch to just the SOC
> maintainers and the ARM mailing list, not all of them listed above.
>
> git send-email --to jason@lakedaemon.net --to andrew@lunn.ch --to
> sebastian.hesselbarth@gmail.com --to
> gregory.clement@free-electrons.com
> 0001-ARM-mv78xx0-remove-unused-header.patch --cc
> linux-arm-kernel@lists.infradead.org
>
> In your case, you'll most likely pick Cc the outreachy mailing list
> and send it to Greg KH (as Greg just said).
For staging patches, please also cc: the public mailing list for the
staging drivers, and any other maintainers of the drivers, they want to
see these patches as well.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 17:48 ` Ezequiel Garcia
2018-02-15 17:57 ` Greg KH
@ 2018-02-15 19:58 ` Julia Lawall
1 sibling, 0 replies; 9+ messages in thread
From: Julia Lawall @ 2018-02-15 19:58 UTC (permalink / raw)
To: Ezequiel Garcia; +Cc: Dafna Hirschfeld, outreachy-kernel
[-- Attachment #1: Type: text/plain, Size: 3853 bytes --]
On Thu, 15 Feb 2018, Ezequiel Garcia wrote:
> On 15 February 2018 at 14:42, Ezequiel Garcia
> <ezequiel@vanguardiasur.com.ar> wrote:
> > On 15 February 2018 at 14:32, Dafna Hirschfeld <dafna3@gmail.com> wrote:
> >> Hi,
> >> I follow the first-patch tutorial.
> >> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> >> <gregkh@linuxfoundation.org>.
> >> Should I send the patch to this mailing list and add the maintainer as a CC,
> >> or should I send two separate mails, one to this mailing list and one to the
> >> maintainer ?
> >>
> >
> > Just like Shraddha said, you sould send just *one* mail.
> >
> > You can Cc as much developers as you want, but you'll usually want to keep
> > the Cc list short, Ccing only the relevant maintainers.
> >
> > Let's work with an example. I just crafted a small patch removing an unused
> > header from arch/arm/mach-mv78xx0/common.c:
> >
> > commit 42dc417bb0c0547a926880494ac3f79829bd3035 (HEAD -> orion-nand)
> > Author: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > Date: Thu Feb 15 14:39:09 2018 -0300
> >
> > ARM: mv78xx0: remove unused header
> >
> > This file doesn't setup an orion-nand device, and so
> > it does not need the orion-nand header.
> >
> > Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> >
> > diff --git a/arch/arm/mach-mv78xx0/common.c b/arch/arm/mach-mv78xx0/common.c
> > index f72e1e9f5fc5..89c95e365e90 100644
> > --- a/arch/arm/mach-mv78xx0/common.c
> > +++ b/arch/arm/mach-mv78xx0/common.c
> > @@ -19,7 +19,6 @@
> > #include <asm/mach/map.h>
> > #include <asm/mach/time.h>
> > #include <linux/platform_data/usb-ehci-orion.h>
> > -#include <linux/platform_data/mtd-orion_nand.h>
> > #include <plat/time.h>
> > #include <plat/common.h>
> > #include <plat/addr-map.h>
> >
>
> Oops... sent the mail by mistake. So, like I was saying: I have that
> patch ready.
> Now I need to see who I'll sent to:
>
> ./scripts/get_maintainer.pl 0001-ARM-mv78xx0-remove-unused-header.patch
> Jason Cooper <jason@lakedaemon.net> (maintainer:ARM/Marvell
> Dove/MV78xx0/Orion SOC support)
> Andrew Lunn <andrew@lunn.ch> (maintainer:ARM/Marvell
> Dove/MV78xx0/Orion SOC support)
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> Gregory Clement <gregory.clement@free-electrons.com>
> (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> Russell King <linux@armlinux.org.uk> (maintainer:ARM PORT)
> linux-arm-kernel@lists.infradead.org (moderated list:ARM SUB-ARCHITECTURES)
> linux-kernel@vger.kernel.org (open list)
>
> OK, that's a long list. I'll send the patch to just the SOC
> maintainers and the ARM mailing list, not all of them listed above.
>
> git send-email --to jason@lakedaemon.net --to andrew@lunn.ch --to
> sebastian.hesselbarth@gmail.com --to
> gregory.clement@free-electrons.com
> 0001-ARM-mv78xx0-remove-unused-header.patch --cc
> linux-arm-kernel@lists.infradead.org
>
> In your case, you'll most likely pick Cc the outreachy mailing list
> and send it to Greg KH (as Greg just said).
There is a suggested command line in the tutorial that should limit the
set of people to the actual maintainers.
julia
>
> Hope it helps,
> --
> Ezequiel García, VanguardiaSur
> www.vanguardiasur.com.ar
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/CAAEAJfAwxr5dyHt%3DyjotkdvTWNo5M_DsWvGPMBkD%2BeiHE%2B%2BCEQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 17:57 ` Greg KH
@ 2018-02-15 19:59 ` Julia Lawall
2018-02-16 10:34 ` Greg KH
0 siblings, 1 reply; 9+ messages in thread
From: Julia Lawall @ 2018-02-15 19:59 UTC (permalink / raw)
To: Greg KH; +Cc: Ezequiel Garcia, Dafna Hirschfeld, outreachy-kernel
On Thu, 15 Feb 2018, Greg KH wrote:
> On Thu, Feb 15, 2018 at 02:48:30PM -0300, Ezequiel Garcia wrote:
> > On 15 February 2018 at 14:42, Ezequiel Garcia
> > <ezequiel@vanguardiasur.com.ar> wrote:
> > > On 15 February 2018 at 14:32, Dafna Hirschfeld <dafna3@gmail.com> wrote:
> > >> Hi,
> > >> I follow the first-patch tutorial.
> > >> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> > >> <gregkh@linuxfoundation.org>.
> > >> Should I send the patch to this mailing list and add the maintainer as a CC,
> > >> or should I send two separate mails, one to this mailing list and one to the
> > >> maintainer ?
> > >>
> > >
> > > Just like Shraddha said, you sould send just *one* mail.
> > >
> > > You can Cc as much developers as you want, but you'll usually want to keep
> > > the Cc list short, Ccing only the relevant maintainers.
> > >
> > > Let's work with an example. I just crafted a small patch removing an unused
> > > header from arch/arm/mach-mv78xx0/common.c:
> > >
> > > commit 42dc417bb0c0547a926880494ac3f79829bd3035 (HEAD -> orion-nand)
> > > Author: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > > Date: Thu Feb 15 14:39:09 2018 -0300
> > >
> > > ARM: mv78xx0: remove unused header
> > >
> > > This file doesn't setup an orion-nand device, and so
> > > it does not need the orion-nand header.
> > >
> > > Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > >
> > > diff --git a/arch/arm/mach-mv78xx0/common.c b/arch/arm/mach-mv78xx0/common.c
> > > index f72e1e9f5fc5..89c95e365e90 100644
> > > --- a/arch/arm/mach-mv78xx0/common.c
> > > +++ b/arch/arm/mach-mv78xx0/common.c
> > > @@ -19,7 +19,6 @@
> > > #include <asm/mach/map.h>
> > > #include <asm/mach/time.h>
> > > #include <linux/platform_data/usb-ehci-orion.h>
> > > -#include <linux/platform_data/mtd-orion_nand.h>
> > > #include <plat/time.h>
> > > #include <plat/common.h>
> > > #include <plat/addr-map.h>
> > >
> >
> > Oops... sent the mail by mistake. So, like I was saying: I have that
> > patch ready.
> > Now I need to see who I'll sent to:
> >
> > ./scripts/get_maintainer.pl 0001-ARM-mv78xx0-remove-unused-header.patch
> > Jason Cooper <jason@lakedaemon.net> (maintainer:ARM/Marvell
> > Dove/MV78xx0/Orion SOC support)
> > Andrew Lunn <andrew@lunn.ch> (maintainer:ARM/Marvell
> > Dove/MV78xx0/Orion SOC support)
> > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> > (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> > Gregory Clement <gregory.clement@free-electrons.com>
> > (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> > Russell King <linux@armlinux.org.uk> (maintainer:ARM PORT)
> > linux-arm-kernel@lists.infradead.org (moderated list:ARM SUB-ARCHITECTURES)
> > linux-kernel@vger.kernel.org (open list)
> >
> > OK, that's a long list. I'll send the patch to just the SOC
> > maintainers and the ARM mailing list, not all of them listed above.
> >
> > git send-email --to jason@lakedaemon.net --to andrew@lunn.ch --to
> > sebastian.hesselbarth@gmail.com --to
> > gregory.clement@free-electrons.com
> > 0001-ARM-mv78xx0-remove-unused-header.patch --cc
> > linux-arm-kernel@lists.infradead.org
> >
> > In your case, you'll most likely pick Cc the outreachy mailing list
> > and send it to Greg KH (as Greg just said).
>
> For staging patches, please also cc: the public mailing list for the
> staging drivers, and any other maintainers of the drivers, they want to
> see these patches as well.
The suggested get_maintainer command includes -nol, ie no lists. I can
drop that, if we want to include lists.
julia
>
> thanks,
>
> greg k-h
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20180215175724.GA14180%40kroah.com.
> For more options, visit https://groups.google.com/d/optout.
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Outreachy kernel] who to send first patch to
2018-02-15 19:59 ` Julia Lawall
@ 2018-02-16 10:34 ` Greg KH
0 siblings, 0 replies; 9+ messages in thread
From: Greg KH @ 2018-02-16 10:34 UTC (permalink / raw)
To: Julia Lawall; +Cc: Ezequiel Garcia, Dafna Hirschfeld, outreachy-kernel
On Thu, Feb 15, 2018 at 08:59:38PM +0100, Julia Lawall wrote:
>
>
> On Thu, 15 Feb 2018, Greg KH wrote:
>
> > On Thu, Feb 15, 2018 at 02:48:30PM -0300, Ezequiel Garcia wrote:
> > > On 15 February 2018 at 14:42, Ezequiel Garcia
> > > <ezequiel@vanguardiasur.com.ar> wrote:
> > > > On 15 February 2018 at 14:32, Dafna Hirschfeld <dafna3@gmail.com> wrote:
> > > >> Hi,
> > > >> I follow the first-patch tutorial.
> > > >> When running the get_maintainer.sh script, I get Greg Kroah-Hartman
> > > >> <gregkh@linuxfoundation.org>.
> > > >> Should I send the patch to this mailing list and add the maintainer as a CC,
> > > >> or should I send two separate mails, one to this mailing list and one to the
> > > >> maintainer ?
> > > >>
> > > >
> > > > Just like Shraddha said, you sould send just *one* mail.
> > > >
> > > > You can Cc as much developers as you want, but you'll usually want to keep
> > > > the Cc list short, Ccing only the relevant maintainers.
> > > >
> > > > Let's work with an example. I just crafted a small patch removing an unused
> > > > header from arch/arm/mach-mv78xx0/common.c:
> > > >
> > > > commit 42dc417bb0c0547a926880494ac3f79829bd3035 (HEAD -> orion-nand)
> > > > Author: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > > > Date: Thu Feb 15 14:39:09 2018 -0300
> > > >
> > > > ARM: mv78xx0: remove unused header
> > > >
> > > > This file doesn't setup an orion-nand device, and so
> > > > it does not need the orion-nand header.
> > > >
> > > > Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > > >
> > > > diff --git a/arch/arm/mach-mv78xx0/common.c b/arch/arm/mach-mv78xx0/common.c
> > > > index f72e1e9f5fc5..89c95e365e90 100644
> > > > --- a/arch/arm/mach-mv78xx0/common.c
> > > > +++ b/arch/arm/mach-mv78xx0/common.c
> > > > @@ -19,7 +19,6 @@
> > > > #include <asm/mach/map.h>
> > > > #include <asm/mach/time.h>
> > > > #include <linux/platform_data/usb-ehci-orion.h>
> > > > -#include <linux/platform_data/mtd-orion_nand.h>
> > > > #include <plat/time.h>
> > > > #include <plat/common.h>
> > > > #include <plat/addr-map.h>
> > > >
> > >
> > > Oops... sent the mail by mistake. So, like I was saying: I have that
> > > patch ready.
> > > Now I need to see who I'll sent to:
> > >
> > > ./scripts/get_maintainer.pl 0001-ARM-mv78xx0-remove-unused-header.patch
> > > Jason Cooper <jason@lakedaemon.net> (maintainer:ARM/Marvell
> > > Dove/MV78xx0/Orion SOC support)
> > > Andrew Lunn <andrew@lunn.ch> (maintainer:ARM/Marvell
> > > Dove/MV78xx0/Orion SOC support)
> > > Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> > > (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> > > Gregory Clement <gregory.clement@free-electrons.com>
> > > (maintainer:ARM/Marvell Dove/MV78xx0/Orion SOC support)
> > > Russell King <linux@armlinux.org.uk> (maintainer:ARM PORT)
> > > linux-arm-kernel@lists.infradead.org (moderated list:ARM SUB-ARCHITECTURES)
> > > linux-kernel@vger.kernel.org (open list)
> > >
> > > OK, that's a long list. I'll send the patch to just the SOC
> > > maintainers and the ARM mailing list, not all of them listed above.
> > >
> > > git send-email --to jason@lakedaemon.net --to andrew@lunn.ch --to
> > > sebastian.hesselbarth@gmail.com --to
> > > gregory.clement@free-electrons.com
> > > 0001-ARM-mv78xx0-remove-unused-header.patch --cc
> > > linux-arm-kernel@lists.infradead.org
> > >
> > > In your case, you'll most likely pick Cc the outreachy mailing list
> > > and send it to Greg KH (as Greg just said).
> >
> > For staging patches, please also cc: the public mailing list for the
> > staging drivers, and any other maintainers of the drivers, they want to
> > see these patches as well.
>
> The suggested get_maintainer command includes -nol, ie no lists. I can
> drop that, if we want to include lists.
Hm, let's leave it as-is for now, as long as we are including the
maintainers of the drivers, that should be sufficient.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-02-16 10:34 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-15 17:32 who to send first patch to Dafna Hirschfeld
[not found] ` <20180215173939.GA371@shraddha>
2018-02-15 17:40 ` Fwd: [Outreachy kernel] " Shraddha Barke
2018-02-15 17:42 ` Ezequiel Garcia
2018-02-15 17:48 ` Ezequiel Garcia
2018-02-15 17:57 ` Greg KH
2018-02-15 19:59 ` Julia Lawall
2018-02-16 10:34 ` Greg KH
2018-02-15 19:58 ` Julia Lawall
2018-02-15 17:46 ` Greg KH
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.