From: Viresh Kumar <viresh.kumar@linaro.org>
To: Shuosheng Huang <huangshuosheng@allwinnertech.com>
Cc: tiny.windzz@gmail.com, rjw@rjwysocki.net, mripard@kernel.org,
wens@csie.org, jernej.skrabec@siol.net, samuel@sholland.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/6] cpufreq: sun50i: add efuse_xlate to get efuse version.
Date: Tue, 8 Dec 2020 12:59:41 +0530 [thread overview]
Message-ID: <20201208072941.7xbqbolo6mct6niz@vireshk-i7> (raw)
In-Reply-To: <20201208071928.2078-1-huangshuosheng@allwinnertech.com>
Please use --thread=shallow while creating the patches, I use the following
options normally, so they appear as a thread.
git format-patch -C -M --thread=shallow
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Shuosheng Huang <huangshuosheng@allwinnertech.com>
Cc: jernej.skrabec@siol.net, samuel@sholland.org,
tiny.windzz@gmail.com, linux-pm@vger.kernel.org,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
mripard@kernel.org, wens@csie.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/6] cpufreq: sun50i: add efuse_xlate to get efuse version.
Date: Tue, 8 Dec 2020 12:59:41 +0530 [thread overview]
Message-ID: <20201208072941.7xbqbolo6mct6niz@vireshk-i7> (raw)
In-Reply-To: <20201208071928.2078-1-huangshuosheng@allwinnertech.com>
Please use --thread=shallow while creating the patches, I use the following
options normally, so they appear as a thread.
git format-patch -C -M --thread=shallow
--
viresh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-08 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 7:19 [PATCH v4 1/6] cpufreq: sun50i: add efuse_xlate to get efuse version Shuosheng Huang
2020-12-08 7:19 ` Shuosheng Huang
2020-12-08 7:29 ` Viresh Kumar [this message]
2020-12-08 7:29 ` Viresh Kumar
2020-12-08 8:21 ` Maxime Ripard
2020-12-08 8:21 ` Maxime Ripard
2020-12-14 0:46 ` Samuel Holland
2020-12-14 0:46 ` Samuel Holland
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=20201208072941.7xbqbolo6mct6niz@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=huangshuosheng@allwinnertech.com \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=samuel@sholland.org \
--cc=tiny.windzz@gmail.com \
--cc=wens@csie.org \
/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.