From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Sumitra Sharma <sumitraartsy@gmail.com>, outreachy@lists.linux.dev
Cc: alison.schofield@intel.com, julia.lawall@inria.fr
Subject: Re: [Outreachy Info] Ask for help finding cleanups
Date: Thu, 16 Mar 2023 16:41:38 +0100 [thread overview]
Message-ID: <3217711.oiGErgHkdL@suse> (raw)
In-Reply-To: <20230316131656.GB47401@sumitra.com>
On giovedì 16 marzo 2023 14:16:56 CET Sumitra Sharma wrote:
> On Tue, Mar 14, 2023 at 04:49:20PM -0700, Alison Schofield wrote:
> > Hi Applicants,
> >
> > We want to support you finding cleanups. Today I spent some time
> > looking through staging and am working up a small todo list that
> > may be useful.
> >
> > I posted one such cleanup to Menna because I saw them submit a
> > couple of attempts at a first patches.
> >
> > I think that Kloudifold, Khadija, and Sumitra are busy iterating on
> > their first patches. Keep going! Ask for help finding your second
> > patch if needed.
>
> Hi Alison,
>
> My first patch is accepted. I will appreciate if you could help me to find a
> second patch.
I don't want to answer for Alison, however I would like to point out that in
this same thread there are several suggestions, both from Alison and Julia, on
how to find tasks in "driver/staging".
Scroll through the thread again and see if it helps you find more tasks.
Alison's first post explains an effective way to find something in drivers/
staging
Thank you,
Fabio
PS: I think applicants shouldn't overlook Julia's post about certain macros
evaluating in container_of(). As Julia suggested, you can work on converting
these macros into function definitions.
Furthermore, this kind of work would help to understand the working and
implementation details of container_of(), itself a macro used a lot in the
drivers and core subsystems of the entire Kernel.
Isn't anyone interested in this kind of tasks? Please have a look at https://
lore.kernel.org/outreachy/124d2ef9-6f1d-2652-c88d-161f1bc06443@inria.fr/
> Regards,
>
> Sumitra
>
> > Anyone else who wants help in finding their first patch, please reach
> > out. I imagine their are some folks exploring here, that I haven't
> > met on the list yet.
> >
> > Finally, it seems we won't be holding to the traditional 10 cleanup
> > patch requirement this round! Please continue your efforts and I'll
> > redirect you towards projects after a 'few' cleanup patches are
> > accepted into staging.
> > Thanks,
> > Alison
prev parent reply other threads:[~2023-03-16 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 23:49 [Outreachy Info] Ask for help finding cleanups Alison Schofield
2023-03-15 7:44 ` Mark Heim
2023-03-15 18:12 ` Alison Schofield
[not found] ` <CALfc2nhr7fWD33T5000kJt9stcgQ3fJM8YNTQhRgozxFYDxyYw@mail.gmail.com>
2023-03-16 14:53 ` Alison Schofield
[not found] ` <CALfc2nioOy+T7GyV==Akr5WY5gC_awadai77k4tqr-NGNhaR+A@mail.gmail.com>
2023-03-17 1:51 ` Alison Schofield
2023-03-15 9:10 ` Menna Mahmoud
2023-03-15 9:19 ` Julia Lawall
2023-03-15 9:25 ` Menna Mahmoud
[not found] ` <CAOHb_39SAEOwJOCNqsvND5w81MbAHLROf+sRAu0AWi911teidA@mail.gmail.com>
2023-03-15 16:19 ` Alison Schofield
2023-03-16 13:16 ` Sumitra Sharma
2023-03-16 15:07 ` Alison Schofield
2023-03-16 15:27 ` Sumitra Sharma
2023-03-16 15:41 ` Fabio M. De Francesco [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=3217711.oiGErgHkdL@suse \
--to=fmdefrancesco@gmail.com \
--cc=alison.schofield@intel.com \
--cc=julia.lawall@inria.fr \
--cc=outreachy@lists.linux.dev \
--cc=sumitraartsy@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