linux-safety.lists.elisa.tech archive mirror
 help / color / mirror / Atom feed
From: "Sudip Mukherjee" <sudip.mukherjee@codethink.co.uk>
To: Milan Lakhani <milan.lakhani@codethink.co.uk>,
	linux-safety@lists.elisa.tech
Subject: Re: [linux-safety] E-mail addresses for kernel contributors to send patches to
Date: Wed, 16 Dec 2020 16:30:46 +0000	[thread overview]
Message-ID: <43a21360-7869-fa66-9895-91f8d3118ca9@codethink.co.uk> (raw)
In-Reply-To: <05356dac-c547-e71c-7ec4-f474d5ad655e@codethink.co.uk>

Hi Milan,

On 16/12/2020 16:16, Milan Lakhani wrote:
> Hi,
> 
> I made the below changes and sent the documentation patch version 2,
> 

<snip>

> 
> For driver patches I'll also include devel@driverdev.osuosl.org and Greg
> gregkh@linuxfoundation.org, while for a documentation patch I'll include
> the linux-doc@vger.kernel.org list.

Not for all the drivers. Like any patch to drivers in
'drivers/watchdog/' does not need GregKH or devel@driverdev.osuosl.org.



-- 
Regards
Sudip


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#227): https://lists.elisa.tech/g/linux-safety/message/227
Mute This Topic: https://lists.elisa.tech/mt/79004338/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-



      parent reply	other threads:[~2020-12-16 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 19:50 [linux-safety] [PATCH] Documentation: process: Correct numbering Milan Lakhani
2020-12-15 20:16 ` Sudip Mukherjee
2020-12-15 20:32   ` Milan Lakhani
2020-12-16 16:16     ` [linux-safety] E-mail addresses for kernel contributors to send patches to Milan Lakhani
2020-12-16 16:23       ` Lukas Bulwahn
2020-12-16 16:30       ` Sudip Mukherjee [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=43a21360-7869-fa66-9895-91f8d3118ca9@codethink.co.uk \
    --to=sudip.mukherjee@codethink.co.uk \
    --cc=linux-safety@lists.elisa.tech \
    --cc=milan.lakhani@codethink.co.uk \
    /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).