All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Karolina Drobnik <karolinadrobnik@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
	 Outreachy Linux Kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Help maintain the First Patch Tutorial
Date: Tue, 19 Oct 2021 11:04:43 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2110191104280.2643@hadrien> (raw)
In-Reply-To: <11393669909cdb43a5f0ca99eace0451bca45d30.camel@gmail.com>



On Tue, 19 Oct 2021, Karolina Drobnik wrote:

> Hi,
>
> Thank you very much for your comments. You can find an updated version
> of this section below.


OK for me.  Thanks!

julia

>
>
> Thanks,
> Karolina
>
> ------------------------------------------------------------
>
> <<Anchor(submit_a_patch)>>
> = Submit a patch =
>
> The first step to sending a patch is to figure out who to send it to.
> For this, you need to find the maintainer of the code you're patching,
> and Cc the correct mailing list. If you simply send it off to
> linux-kernel@vger.kernel.org, it will get ignored. The perl script in
> the kernel source directory ``scripts/get_maintainer.pl`` will either
> take a git commit or a file, and tell you who to send your patch to:
>
> {{{
> $ git show --pretty=oneline --abbrev-commit HEAD
> a490e2e84eda staging: vt6655: Rename byPreambleType field
> diff --git a/drivers/staging/vt6655/baseband.c
> b/drivers/staging/vt6655/baseband.c
> index 0bae35af6e0f..5efca92f1f18 100644
> --- a/drivers/staging/vt6655/baseband.c
> +++ b/drivers/staging/vt6655/baseband.c
> @@ -1764,7 +1764,7 @@ void vnt_get_phy_field(struct vnt_private *priv,
> u32 frame_length,
>         u32 count = 0;
>         u32 tmp;
>         int ext_bit;
> -       u8 preamble_type = priv->byPreambleType;
> +       u8 preamble_type = priv->preamble_type;
>
>         bit_count = frame_length * 8;
>         ext_bit = false;
>
> $ git show HEAD | perl scripts/get_maintainer.pl --separator , --
> nokeywords --nogit --nogit-fallback --norolestats
> Forest Bond <forest@alittletooquiet.net>,Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>,linux-staging@lists.linux.dev,linux-kernel@vger.kernel.org
> }}}
>
> To get a list of maintainers for a particular file, use `-f` option:
>
> {{{
> $ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --
> nogit-fallback --norolestats -f drivers/staging/vt6655/baseband.c
> Forest Bond <forest@alittletooquiet.net>,Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>,linux-staging@lists.linux.dev,linux-kernel@vger.kernel.org
> }}}
>
> The many arguments to get_maintainer.pl cause the output to be in the
> form of a comma-separated list and cause only the actual maintainers of
> the affected files and relevant mailing lists to be included. For
> Outreachy patches, remember to include the outreachy mailing list in
> your `To:` field as well.
>
> The second step to submitting a patch is to create and send a patch as
> an email. You cannot send patches as attachments to the mailing list.
> Instead, you will have to craft a special email, and send the patch
> inline.
>
> There are two ways to send a patch. Either way is correct, and we
> suggest you get comfortable with sending patches both ways. We suggest
> sending your first patch to yourself, in order to make sure it works.
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/11393669909cdb43a5f0ca99eace0451bca45d30.camel%40gmail.com.
>


  reply	other threads:[~2021-10-19  9:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 17:42 Help maintain the First Patch Tutorial Alison Schofield
2021-10-18  9:59 ` [Outreachy kernel] " Karolina Drobnik
2021-10-18 10:12   ` Julia Lawall
2021-10-18 14:01     ` Karolina Drobnik
2021-10-18 14:18       ` Julia Lawall
2021-10-18 17:54   ` Alison Schofield
2021-10-19  6:19     ` Greg KH
2021-10-19 15:36       ` Alison Schofield
2021-10-19 15:52         ` Greg KH
2021-10-20 13:00         ` Karolina Drobnik
2021-10-20 14:50           ` Alison Schofield
2021-10-19  9:01     ` Karolina Drobnik
2021-10-19  9:04       ` Julia Lawall [this message]
2021-10-25 11:44 ` Karolina Drobnik
2021-10-25 16:30   ` Alison Schofield
2021-10-26 12:33     ` Karolina Drobnik
2021-10-27 14:48     ` Karolina Drobnik
2021-10-27 19:20       ` Alison Schofield

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=alpine.DEB.2.22.394.2110191104280.2643@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=alison.schofield@intel.com \
    --cc=karolinadrobnik@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 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.