From: Dmitry Osipenko <digetx@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mantravadi Karthik <mkarthik@nvidia.com>,
Shardar Mohammed <smohammed@nvidia.com>,
Timo Alho <talho@nvidia.com>
Cc: "wsa@the-dreams.de" <wsa@the-dreams.de>,
"peda@axentia.se" <peda@axentia.se>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH V19 1/7] i2c: tegra: sort all the include headers alphabetically
Date: Tue, 12 Feb 2019 21:42:19 +0300 [thread overview]
Message-ID: <7143cefd-8c8f-e010-90db-5ac46aa96105@gmail.com> (raw)
In-Reply-To: <BYAPR12MB3398679040C6ED2E129CEBFBC2650@BYAPR12MB3398.namprd12.prod.outlook.com>
12.02.2019 21:32, Sowjanya Komatineni пишет:
> Please ignore all Patch V19 series. Will resend.
>
> Dmitry/Thierry
> I am using below stable tags in commit message based on V18 feedback to get patch applied to old kernels
> Git send email considers whole text after Cc as email address and reports badly formatted address.
>
> Is there any format that I should follow to specify kernel versions along with stable tag?
>
> Cc: stable@vger.kernel.org # 4.4+
> Cc: stable@vger.kernel.org # 4.20+
You could ask send-email to not auto-include CC's from the commit message:
git send-email --suppress-cc=all
Also see https://git-scm.com/docs/git-send-email#git-send-email---suppress-ccltcategorygt for more options.
next prev parent reply other threads:[~2019-02-12 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:27 [PATCH V19 1/7] i2c: tegra: sort all the include headers alphabetically Sowjanya Komatineni
2019-02-12 18:27 ` [PATCH V19 2/7] i2c: tegra: add bus clear Master Support Sowjanya Komatineni
2019-02-12 18:32 ` [PATCH V19 1/7] i2c: tegra: sort all the include headers alphabetically Sowjanya Komatineni
2019-02-12 18:42 ` Dmitry Osipenko [this message]
2019-02-12 18:45 ` Sowjanya Komatineni
-- strict thread matches above, loose matches on Subject: below --
2019-02-12 18:28 Sowjanya Komatineni
2019-02-12 19:06 Sowjanya Komatineni
2019-02-12 21:00 ` Peter Rosin
2019-02-12 21:15 ` Dmitry Osipenko
2019-02-13 8:35 ` Wolfram Sang
2019-02-13 13:13 ` Dmitry Osipenko
2019-02-13 14:55 ` Wolfram Sang
2019-02-13 23:45 ` Sowjanya Komatineni
2019-02-14 16:51 ` Wolfram Sang
2019-02-14 16:51 ` Wolfram Sang
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=7143cefd-8c8f-e010-90db-5ac46aa96105@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkarthik@nvidia.com \
--cc=peda@axentia.se \
--cc=skomatineni@nvidia.com \
--cc=smohammed@nvidia.com \
--cc=talho@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=wsa@the-dreams.de \
/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