From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Deepak R Varma <drv@mailo.com>, Kloudifold <cloudifold.3125@gmail.com>
Cc: outreachy@lists.linux.dev, teddy.wang@siliconmotion.com,
sudipm.mukherjee@gmail.com, gregkh@linuxfoundation.org,
alison.schofield@intel.com, linuxstaging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: sm750: Rename sm750_hw_cursor_* functions to snake_case
Date: Tue, 21 Mar 2023 15:15:41 +0700 [thread overview]
Message-ID: <ZBlnrWywCfDftf0+@debian.me> (raw)
In-Reply-To: <ZBiEnFxlHb/OES0B@ubun2204.myguest.virtualbox.org>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Mon, Mar 20, 2023 at 09:36:52PM +0530, Deepak R Varma wrote:
> Hello,
> Looks like you missed some maintainer list recipients in your to/cc of this
> patch. How are you extracting the maintainer list?
The easiest way to copy the list is by passing `--norolestats
--separator , ` to get_maintainer.pl.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-21 8:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 5:07 [PATCH v4] staging: sm750: Rename sm750_hw_cursor_* functions to snake_case Kloudifold
2023-03-20 16:06 ` Deepak R Varma
2023-03-21 8:15 ` Bagas Sanjaya [this message]
2023-03-21 9:55 ` Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2023-03-20 5:14 Kloudifold
2023-03-20 5:31 ` Dan Carpenter
2023-03-20 7:45 ` Julia Lawall
2023-03-21 8:20 ` Bagas Sanjaya
2023-03-21 8:37 ` Dan Carpenter
2023-03-22 9:01 ` Dan Carpenter
[not found] ` <CAM44cXOB3kA03Ay6c5PO_eOkS7npa00A4mQnEj2ahubRPE+MDg@mail.gmail.com>
[not found] ` <f56002cc-78a1-4972-b66a-b41f7bf124e1@kili.mountain>
[not found] ` <CAM44cXOgi8pektFFF_sGWZED3LsiHkRPO3WP4skekNWJ+WY=KA@mail.gmail.com>
2023-03-31 4:32 ` Dan Carpenter
2023-03-31 16:32 ` Alison Schofield
2023-03-31 16:37 ` Greg KH
2023-03-19 15:32 Kloudifold
2023-03-22 18:48 ` Ira Weiny
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=ZBlnrWywCfDftf0+@debian.me \
--to=bagasdotme@gmail.com \
--cc=alison.schofield@intel.com \
--cc=cloudifold.3125@gmail.com \
--cc=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxstaging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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.