From: Dan Carpenter <dan.carpenter@oracle.com>
To: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lee Jones <lee.jones@linaro.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Christian Gromm <christian.gromm@microchip.com>
Subject: Re: [PATCH] staging: most: dim2: fix device registration
Date: Tue, 5 Oct 2021 17:17:55 +0300 [thread overview]
Message-ID: <20211005141754.GX2048@kadam> (raw)
In-Reply-To: <d309b4cf-12f5-5f49-fcbe-3141dff9e73f@cogentembedded.com>
On Tue, Oct 05, 2021 at 04:33:02PM +0300, Nikita Yushchenko wrote:
> > Also, why have you not cc:ed the original author of the commit you are
> > "fixing" here? They are the maintainer of this code, right?
>
> I was under impression that "git send-email" does that automatically...
>
The ./scripts/get_maintainer.pl does try to CC them. It's working for
me when I use the script on your patch. I normally put the author in
the To: header so it's more likely they'll see my patch and Ack it.
regards,
dan carpenter
next prev parent reply other threads:[~2021-10-05 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 20:56 [PATCH] staging: most: dim2: fix device registration Nikita Yushchenko
2021-10-05 10:27 ` Greg Kroah-Hartman
2021-10-05 13:33 ` Nikita Yushchenko
2021-10-05 13:49 ` Greg Kroah-Hartman
2021-10-05 14:07 ` Greg Kroah-Hartman
2021-10-05 14:17 ` Dan Carpenter [this message]
2021-10-05 14:34 ` [PATCH 1/2] staging: most: dim2: do not double-register the same device Nikita Yushchenko
2021-10-10 6:27 ` Greg Kroah-Hartman
2021-10-11 6:11 ` [PATCH v2 " Nikita Yushchenko
2021-10-12 12:59 ` Christian.Gromm
2021-10-05 14:34 ` [PATCH 2/2] staging: most: dim2: use device release method Nikita Yushchenko
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=20211005141754.GX2048@kadam \
--to=dan.carpenter@oracle.com \
--cc=christian.gromm@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nikita.yoush@cogentembedded.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.