From: Shuah Khan <skhan@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Vinayak Hegde <vinayakph123@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] Linux 6.1.9
Date: Fri, 3 Feb 2023 09:46:41 -0700 [thread overview]
Message-ID: <df93cbb8-0097-db63-5e0d-b7dd2ec1ea55@linuxfoundation.org> (raw)
In-Reply-To: <48e1ae98-8f29-96d2-61af-d79ce22dcc62@gmail.com>
On 2/3/23 03:12, Bagas Sanjaya wrote:
> On 2/3/23 16:42, Vinayak Hegde wrote:
>> Hi Everyone,
>> I was going through A Beginner's Guide to Linux Kernel Development (LFD103) course and was trying out a few things
>> mistakenly sending this mail.
>>
>
> Hi and welcome to LKML!
>
> Some netiquette tips:
>
> * Don't top-post when replying; reply inline with appropriate context
> instead. Some people (like me) tends to cut quoted reply below
> if you top-post.
> * Don't send HTML emails - many kernel development lists (including
> LKML) don't like them for being common spam method.
> * Wait for at least a day before replying - people may respond to
> your message at different pace.
> * Use git-send-email(1) to submit patches (see
> Documentation/process/submitting-patches.rst for how to do that).
>> Regarding your patch, I think Greg has already bumped SUBLEVEL
> whenever new stable release is made, so no need to send separate
> patch just for that.
>
[Trimmed the email list to reduce noise.]
If you read this email more carefully, you would have noticed that this
email was sent by mistake while taking LFD103 class. The sender said this
isn't a patch.
thanks,
-- Shuah
prev parent reply other threads:[~2023-02-03 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230203093811.2678-1-vinayakph123@gmail.com>
[not found] ` <CAJesESYM1URn3_hMjPoMkfFo=5k-Yb9HZuyy9__kyKoZPoAsRA@mail.gmail.com>
2023-02-03 10:12 ` Bagas Sanjaya
2023-02-03 16:46 ` Shuah Khan [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=df93cbb8-0097-db63-5e0d-b7dd2ec1ea55@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vinayakph123@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
all inboxes | Powered by JetHome®