From: Alison Schofield <alison.schofield@intel.com>
To: Jaehee Park <jhpark1013@gmail.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: Finding Clean-up Tasks
Date: Fri, 1 Apr 2022 08:20:15 -0700 [thread overview]
Message-ID: <20220401152015.GA1186574@alison-desk> (raw)
In-Reply-To: <20220401142803.GA38814@jaehee-ThinkPad-X1-Extreme>
On Fri, Apr 01, 2022 at 10:28:03AM -0400, Jaehee Park wrote:
> On Thu, Mar 31, 2022 at 11:38:05AM -0700, Alison Schofield wrote:
snip
> > Confidence to send the patch:
> > -----------------------------
> > Go ahead and search on this mailing list for the checkpatch
> > string. You should find many examples that match what you
> > are about to do. See what worked well, what needed rework.
> >
> > If you have a patch AND a question, you can send the patch
> > and put your question below the scissors line. For example,
> > you might see multiple instances of something but are not sure
> > the patch will be well-received. Fix one instance - and below
> > the scissor line ask you question: "There are 10 more of these
> > in this file, just want to sanity check that my approach here
> > is wanted." (If I were doing cleanup today, I'd use this tactic
> > for drivers/staging/iio checkpatch ERROR about octals.)
> >
>
> Thank you for advice! I had a question about where to put the questions
> in the patch. When you say scissor line, are we putting dashed lined
> somewhere in the patch and writing our questions? Or did you mean we
> should reply to our patch?
>
Below the 'scissor line' is the same place you would place a Changelog
when versioning the patch. Anything below the "---" and before the
diffstat gets automagically tossed when the patch is applied.
So, it looks something like this:
>> bssid_filter and num_of_ssids have the ssid separated from the rest of
>> the words with an underscore.
>>
>> Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
>> ---
Insert question, additional comment here.
In the future, you'll learn about RFC patches, where we are sometimes
asking for a greater conceptual review before posting. But, for small
questions about a specific patch - this space works well.
>> drivers/staging/wfx/hif_tx.c | 10 +++++-----
>> drivers/staging/wfx/sta.c | 20 ++++++++++----------
>> 2 files changed, 15 insertions(+), 15 deletions(-)
Alison
prev parent reply other threads:[~2022-04-01 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 18:38 Finding Clean-up Tasks Alison Schofield
2022-03-31 18:50 ` Alison Schofield
2022-04-01 14:28 ` Jaehee Park
2022-04-01 15:08 ` Stefano Brivio
2022-04-01 15:18 ` Jaehee Park
2022-04-01 15:14 ` Fabio M. De Francesco
2022-04-01 15:17 ` Jaehee Park
2022-04-01 15:20 ` 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=20220401152015.GA1186574@alison-desk \
--to=alison.schofield@intel.com \
--cc=jhpark1013@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.