All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Ramji Jiyani <ramjiyani@google.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: Fix comment typo in scripts/Makefile.modpost
Date: Sun, 19 Sep 2021 11:01:50 +0900	[thread overview]
Message-ID: <CAK7LNAQE_pEWaHP1GgJ57VJ1FCStDjf+mS5uvpGP=SxpNG0DOA@mail.gmail.com> (raw)
In-Reply-To: <20210916092122.2374583-1-ramjiyani@google.com>

On Thu, Sep 16, 2021 at 6:21 PM Ramji Jiyani <ramjiyani@google.com> wrote:
>
> Change comment "create one <module>.mod.c file pr. module"
> to "create one <module>.mod.c file per module"
>
> Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
> ---
>  scripts/Makefile.modpost | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to linux-kbuild. Thanks.


> diff --git a/scripts/Makefile.modpost b/scripts/Makefile.modpost
> index eef56d629799..48585c4d04ad 100644
> --- a/scripts/Makefile.modpost
> +++ b/scripts/Makefile.modpost
> @@ -13,7 +13,7 @@
>  # Stage 2 is handled by this file and does the following
>  # 1) Find all modules listed in modules.order
>  # 2) modpost is then used to
> -# 3)  create one <module>.mod.c file pr. module
> +# 3)  create one <module>.mod.c file per module
>  # 4)  create one Module.symvers file with CRC for all exported symbols
>
>  # Step 3 is used to place certain information in the module's ELF
> --
> 2.33.0.309.g3052b89438-goog
>


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2021-09-19  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  9:21 [PATCH] kbuild: Fix comment typo in scripts/Makefile.modpost Ramji Jiyani
2021-09-19  2:01 ` Masahiro Yamada [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='CAK7LNAQE_pEWaHP1GgJ57VJ1FCStDjf+mS5uvpGP=SxpNG0DOA@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=ndesaulniers@google.com \
    --cc=ramjiyani@google.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.