Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: outreachy@lists.linux.dev
Subject: Re: [Outreachy Info] Ask for help finding cleanups
Date: Thu, 16 Mar 2023 08:27:12 -0700	[thread overview]
Message-ID: <20230316152712.GA81902@sumitra.com> (raw)
In-Reply-To: <ZBMwpDSM3W2IDso4@aschofie-mobl2>

On Thu, Mar 16, 2023 at 08:07:16AM -0700, Alison Schofield wrote:
> On Thu, Mar 16, 2023 at 06:16:56AM -0700, 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.
> >  
> > Regards,
> > 
> > Sumitra
> 
> Congratulations on getting the patch accepted!
> I do see you sent another patch, and GregKH responded that it needs
> followup. He sent his automatic, problem with commit message and or
> commit log email. Revisit the docs he suggested and the first patch
> tutorial and see if you can come up with a rev 2 where the commit
> message 'says what you did' and the commit log 'says why you did it'.
> 

Hi Alison,

I will work this way, Thank you for your guidance.

Regards,

Sumitra

  reply	other threads:[~2023-03-16 15:27 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 [this message]
2023-03-16 15:41   ` Fabio M. De Francesco

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=20230316152712.GA81902@sumitra.com \
    --to=sumitraartsy@gmail.com \
    --cc=alison.schofield@intel.com \
    --cc=outreachy@lists.linux.dev \
    /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