All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Kloudifold <cloudifold.3125@gmail.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Help in patch message
Date: Tue, 14 Mar 2023 09:15:08 -0700	[thread overview]
Message-ID: <ZBCdjKrfu/qe71bK@aschofie-mobl2> (raw)
In-Reply-To: <ZA/Tql5l6dfNaMZ7@CloudiRingWorld>

On Tue, Mar 14, 2023 at 09:53:46AM +0800, Kloudifold wrote:
> Dear Outreachy Mentors,
> 
> I hope this email finds you well. As an Outreachy applicant,
> I have been working on submitting patches to the kernel, but
> I seem to be having trouble getting them accepted. I have
> read the Outreachy tutorials and tried to follow the best practices,
> but my patch messages keep getting rejected.
> 
> I really wonder if I have some kind of language problem, I don't
> actually know how to say something?
> 
> Recently, I submitted a patch that has been rejected, and I am not
> sure whether to go ahead and fix it or create a new one.
> I would greatly appreciate your guidance on how to proceed
> 
> Thank you for your help and guidance throughout this process.
> I look forward to your response.

Hi Kloudifold,

I echo the other responses here. 
Before you press 'send' on v3, walk thru the tutorial again. There will
be parts that make more sense now that you are doing revisions and 
that you have comments.

It looks like you will be preparing and sending v3 of your camelcase patch.

The biggest thing I see recently is compile errors on your patch, and
others patches. Sometimes lkp finds compile errors in build environments
that are less common, and that is less of a concern. They need to be fixed,
but I don't expect you all to run all build environments. That is what lkp does.

That said, be sure to check for new .o's each time you think you are 
compiling the driver.

Kudos to you for driving one patch to completion before sending out
another!

Keep at it!
Alison

> 
> Best regards,
> 
> Kloudifold
> 
> 

      parent reply	other threads:[~2023-03-14 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  1:53 Help in patch message Kloudifold
2023-03-14  4:40 ` Bagas Sanjaya
2023-03-14  6:13 ` Julia Lawall
2023-03-14  6:30 ` Khadija Kamran
2023-03-14 16:15 ` Alison Schofield [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=ZBCdjKrfu/qe71bK@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=cloudifold.3125@gmail.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 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.