Should we Cc this list when submitting patches for subsystems other than "staging"?

Should we Cc this list when submitting patches for subsystems other than "staging"?

[Fabio M. De Francesco]

Hello,

During the current month I have submitted some patches for subsystems other
than drivers/staging. When I sent them I thought that those shouldn't be 
Cc'ed also to this list. Now I'm not anymore sure if I did it correctly.

My question is if all patches sent by the Outreachy's applicants until 
April 22nd should also be sent to this list, even when they are for 
subsystems other than drivers/staging.

Furthermore, one of the above-mentioned patches is strictly related to one
of the three Linux projects, being it a reworking and extension of a large 
section of the documentation of HIGHMEM. Is it sufficient to add that patch 
to the page where we register our contributions in the Outreachy's website? 

I'm also asking because during these days I'm preparing further patches to
other subsystems and I'm going to submit them well before April 22nd. 

Thanks,

Fabio M. De Francesco

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Alison Schofield]

On Tue, Apr 12, 2022 at 10:21:31PM +0200, Fabio M. De Francesco wrote:
> Hello,
> 
> During the current month I have submitted some patches for subsystems other
> than drivers/staging. When I sent them I thought that those shouldn't be 
> Cc'ed also to this list. Now I'm not anymore sure if I did it correctly.
> 
> My question is if all patches sent by the Outreachy's applicants until 
> April 22nd should also be sent to this list, even when they are for 
> subsystems other than drivers/staging.
> 
> Furthermore, one of the above-mentioned patches is strictly related to one
> of the three Linux projects, being it a reworking and extension of a large 
> section of the documentation of HIGHMEM. Is it sufficient to add that patch 
> to the page where we register our contributions in the Outreachy's website? 
> 
> I'm also asking because during these days I'm preparing further patches to
> other subsystems and I'm going to submit them well before April 22nd. 

Thanks for asking Fabio,

Yes, all contributions that an applicant considers to be part of their
application should be shared on this list.

There's always an exception! Perhaps if a mentor gives out a small
task for which a posting to this list would spoil the task for others,
only gets sent to the mentor(s). I expect project mentors would tell
you that case explicitly.

We like to see everything you all are doing and we want the list archive 
to accurately reflect all contributions and communications.

Alison

> 
> Thanks,
> 
> Fabio M. De Francesco
> 
> 
> 

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Alison Schofield]

On Tue, Apr 12, 2022 at 08:00:24PM -0700, Sevinj Aghayeva wrote:
>    On Tue, Apr 12, 2022 at 6:34 PM Alison Schofield
>    <alison.schofield@intel.com> wrote:
> 
>      On Tue, Apr 12, 2022 at 10:21:31PM +0200, Fabio M. De Francesco wrote:
>      > Hello,
>      >
>      > During the current month I have submitted some patches for subsystems
>      other
>      > than drivers/staging. When I sent them I thought that those shouldn't
>      be
>      > Cc'ed also to this list. Now I'm not anymore sure if I did it
>      correctly.
>      >
>      > My question is if all patches sent by the Outreachy's applicants until
>      > April 22nd should also be sent to this list, even when they are for
>      > subsystems other than drivers/staging.
>      >
>      > Furthermore, one of the above-mentioned patches is strictly related to
>      one
>      > of the three Linux projects, being it a reworking and extension of a
>      large
>      > section of the documentation of HIGHMEM. Is it sufficient to add that
>      patch
>      > to the page where we register our contributions in the Outreachy's
>      website?
>      >
>      > I'm also asking because during these days I'm preparing further
>      patches to
>      > other subsystems and I'm going to submit them well before April 22nd.
> 
>      Thanks for asking Fabio,
> 
>      Yes, all contributions that an applicant considers to be part of their
>      application should be shared on this list.
> 
>      There's always an exception! Perhaps if a mentor gives out a small
>      task for which a posting to this list would spoil the task for others,
>      only gets sent to the mentor(s). I expect project mentors would tell
>      you that case explicitly.
> 
>      We like to see everything you all are doing and we want the list archive
>      to accurately reflect all contributions and communications.
> 
>    Oh, that's good to know. I did a few small patches already, but didn't Cc
>    the list; will do so from now on.
>     

FYI - We have patch reviewers for Outreachy on this list that won't 
see your patch if you omit the list. These reviewers volunteer their
time during the Outreachy contribution period and are familiar with
the Outreachy program.

> 
>      Alison
> 
>      >
>      > Thanks,
>      >
>      > Fabio M. De Francesco
>      >
>      >
>      >
> 
>    --
>    Sevinj.Aghayeva

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Sevinj Aghayeva]

On Wed, Apr 13, 2022 at 12:14 AM Alison Schofield
<alison.schofield@intel.com> wrote:
>
> On Tue, Apr 12, 2022 at 08:00:24PM -0700, Sevinj Aghayeva wrote:
> >    On Tue, Apr 12, 2022 at 6:34 PM Alison Schofield
> >    <alison.schofield@intel.com> wrote:
> >
> >      On Tue, Apr 12, 2022 at 10:21:31PM +0200, Fabio M. De Francesco wrote:
> >      > Hello,
> >      >
> >      > During the current month I have submitted some patches for subsystems
> >      other
> >      > than drivers/staging. When I sent them I thought that those shouldn't
> >      be
> >      > Cc'ed also to this list. Now I'm not anymore sure if I did it
> >      correctly.
> >      >
> >      > My question is if all patches sent by the Outreachy's applicants until
> >      > April 22nd should also be sent to this list, even when they are for
> >      > subsystems other than drivers/staging.
> >      >
> >      > Furthermore, one of the above-mentioned patches is strictly related to
> >      one
> >      > of the three Linux projects, being it a reworking and extension of a
> >      large
> >      > section of the documentation of HIGHMEM. Is it sufficient to add that
> >      patch
> >      > to the page where we register our contributions in the Outreachy's
> >      website?
> >      >
> >      > I'm also asking because during these days I'm preparing further
> >      patches to
> >      > other subsystems and I'm going to submit them well before April 22nd.
> >
> >      Thanks for asking Fabio,
> >
> >      Yes, all contributions that an applicant considers to be part of their
> >      application should be shared on this list.
> >
> >      There's always an exception! Perhaps if a mentor gives out a small
> >      task for which a posting to this list would spoil the task for others,
> >      only gets sent to the mentor(s). I expect project mentors would tell
> >      you that case explicitly.
> >
> >      We like to see everything you all are doing and we want the list archive
> >      to accurately reflect all contributions and communications.
> >
> >    Oh, that's good to know. I did a few small patches already, but didn't Cc
> >    the list; will do so from now on.
> >
>
> FYI - We have patch reviewers for Outreachy on this list that won't
> see your patch if you omit the list. These reviewers volunteer their
> time during the Outreachy contribution period and are familiar with
> the Outreachy program.

How about non-kernel related changes? For example, I'm working on
improving https://mbuto.sh/mbuto/about/ with mentors. It's a script
that builds a minimal image that runs kernel selftests when booted
from; it speeds up testing kernel changes. Should I Cc them to the
list as well?

>
> >
> >      Alison
> >
> >      >
> >      > Thanks,
> >      >
> >      > Fabio M. De Francesco
> >      >
> >      >
> >      >
> >
> >    --
> >    Sevinj.Aghayeva



-- 

Sevinj.Aghayeva

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Alison Schofield]

On Wed, Apr 13, 2022 at 08:14:07AM -0700, Sevinj Aghayeva wrote:
> 
> How about non-kernel related changes? For example, I'm working on
> improving https://mbuto.sh/mbuto/about/ with mentors. It's a script
> that builds a minimal image that runs kernel selftests when booted
> from; it speeds up testing kernel changes. Should I Cc them to the
> list as well?

Sevinj,
Maybe my previous email covered this.
The above sounds like something that all applicants exploring the
networking project would be interested in following.
Alison

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Roopa Prabhu]

On Wed, Apr 13, 2022 at 8:26 AM Alison Schofield
<alison.schofield@intel.com> wrote:
>
> On Wed, Apr 13, 2022 at 08:14:07AM -0700, Sevinj Aghayeva wrote:
> >
> > How about non-kernel related changes? For example, I'm working on
> > improving https://mbuto.sh/mbuto/about/ with mentors. It's a script
> > that builds a minimal image that runs kernel selftests when booted
> > from; it speeds up testing kernel changes. Should I Cc them to the
> > list as well?
>
> Sevinj,
> Maybe my previous email covered this.
> The above sounds like something that all applicants exploring the
> networking project would be interested in following.
> Alison

yes, agree. Stefano and Sevinj's work will make mbuto usable for
everybody (possibly even non-networking folks running selftests).

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Fabio M. De Francesco]

On mercoled? 13 aprile 2022 00:36:03 CEST Alison Schofield wrote:
> On Tue, Apr 12, 2022 at 10:21:31PM +0200, Fabio M. De Francesco wrote:
> > Hello,
> > 
> > During the current month I have submitted some patches for subsystems 
other
> > than drivers/staging. When I sent them I thought that those shouldn't 
be 
> > Cc'ed also to this list. Now I'm not anymore sure if I did it 
correctly.
> > 
> > My question is if all patches sent by the Outreachy's applicants until 
> > April 22nd should also be sent to this list, even when they are for 
> > subsystems other than drivers/staging.
> > 
> > Furthermore, one of the above-mentioned patches is strictly related to 
one
> > of the three Linux projects, being it a reworking and extension of a 
large 
> > section of the documentation of HIGHMEM. Is it sufficient to add that 
patch 
> > to the page where we register our contributions in the Outreachy's 
website? 
> > 
> > I'm also asking because during these days I'm preparing further patches 
to
> > other subsystems and I'm going to submit them well before April 22nd. 
> 
> Thanks for asking Fabio,

Thanks for replying so exhaustively, Alison.

> Yes, all contributions that an applicant considers to be part of their
> application should be shared on this list.

Good to know, but unfortunately now is too late for sharing on this list 
the patches which I've already sent to linux-kernel@vger.kernel.org and 
other lists, but...

> There's always an exception! Perhaps if a mentor gives out a small
> task for which a posting to this list would spoil the task for others,
> only gets sent to the mentor(s). I expect project mentors would tell
> you that case explicitly.
> 
> We like to see everything you all are doing and we want the list archive 
> to accurately reflect all contributions and communications.

In order to let you see everything we did in April, can we send the 
subjects, the commit messages, and the links to lore.kernel.org of those 
patch which we already submitted without Cc'ing this list?

The following is an example of what I'm saying:

-----

https://lore.kernel.org/lkml/20220409012655.9399-1-fmdefrancesco@gmail.com/

ALSA: pcm: Test for "silence" field in array of struct "pcm_format_data"

Syzbot reports "KASAN: null-ptr-deref Write in
snd_pcm_format_set_silence".[1]
    
It is due to missing validation of the "silence" field of struct
"pcm_format_data" in the "pcm_formats" array.
    
Add a test for valid "pat".
    
[1] https://lore.kernel.org/lkml/000000000000d188ef05dc2c7279@google.com/
    
Reported-and-tested-by: 
syzbot+205eb15961852c2c5974@syzkaller.appspotmail.com

-----

This patch has already been merged on April 11, 2022.

What about a list of entries like the one above?

Thanks,

Fabio

Re: Should we Cc this list when submitting patches for subsystems other than "staging"?

[Alison Schofield]

On Wed, Apr 13, 2022 at 12:09:46AM -0700, Fabio M. De Francesco wrote:
> On mercoled? 13 aprile 2022 00:36:03 CEST Alison Schofield wrote:
> > On Tue, Apr 12, 2022 at 10:21:31PM +0200, Fabio M. De Francesco wrote:


> Good to know, but unfortunately now is too late for sharing on this list 
> the patches which I've already sent to linux-kernel@vger.kernel.org and 
> other lists, but...
>

Your patches related to HIGHMEM project are of most interest to this list.
Please 'CC the outreachy list on the next rev of any of those patches,
and 'CC outreachy on any new ones related to HIGHMEM.

Same goes for any patches for memblock and networking projects.

Let's give all applicants easy access to all project related info.

Thanks,
Alison
>