From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
torvalds@linux-foundation.org, masahiroy@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: LOL what a patch! change Linus to Linux
Date: Thu, 21 Jan 2021 13:07:06 -0800 [thread overview]
Message-ID: <215566f1-b016-b42d-089f-bcf09240e9cf@infradead.org> (raw)
In-Reply-To: <20210121143014.8913-1-unixbhaskar@gmail.com>
On 1/21/21 6:30 AM, Bhaskar Chowdhury wrote:
> s/Linus/Linux/
>
> ...how dare I?? :)
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Hi,
You missed a second occurrence of that a few lines later.
However, it is correct as is. It means the kernel tree
that Linus maintains -- sometimes known as mainline.
> ---
> scripts/patch-kernel | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/patch-kernel b/scripts/patch-kernel
> index 033d5916797d..314e80c252c0 100755
> --- a/scripts/patch-kernel
> +++ b/scripts/patch-kernel
> @@ -7,7 +7,7 @@
> # e.g.
> # scripts/patch-kernel . ..
> # Update the kernel tree in the current directory using patches in the
> -# directory above to the latest Linus kernel
> +# directory above to the latest Linux kernel
> # scripts/patch-kernel . .. -ac
> # Get the latest Linux kernel and patch it with the latest ac patch
> # scripts/patch-kernel . .. 2.4.9
> --
> 2.30.0
>
--
~Randy
"He closes his eyes and drops the goggles. You can't get hurt
by looking at a bitmap. Or can you?"
(Neal Stephenson: Snow Crash)
next prev parent reply other threads:[~2021-01-21 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 14:30 [PATCH] scripts: LOL what a patch! change Linus to Linux Bhaskar Chowdhury
2021-01-21 21:07 ` Randy Dunlap [this message]
2021-01-22 4:00 ` Bhaskar Chowdhury
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=215566f1-b016-b42d-089f-bcf09240e9cf@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=unixbhaskar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).