From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] arm64: dts: freescale: Add missing cooling device properties for CPUs
Date: Tue, 3 Jul 2018 18:08:28 +0800 [thread overview]
Message-ID: <20180703100827.GP4348@dragon> (raw)
In-Reply-To: <20180703083431.l4rbnept2lwjocol@vireshk-i7>
On Tue, Jul 03, 2018 at 02:04:31PM +0530, Viresh Kumar wrote:
> On 03-07-18, 15:34, Shawn Guo wrote:
> > Please use my kernel.org email address for future patches.
>
> As there were many patches I relied on get_maintainers to do that
> stuff and it didn't pick you up by default. Maybe try fixing
> MAINTAINERS to add an entry against your email id ?
Good point. Will patch MAINTAINERS for arm64 freescale DTS.
Shawn
next prev parent reply other threads:[~2018-07-03 10:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 5:40 [PATCH 0/6] arm64: dts: Add missing cooling device properties for CPUs Viresh Kumar
2018-05-25 5:40 ` [PATCH 1/6] arm64: dts: amlogic: " Viresh Kumar
2018-05-25 21:10 ` Olof Johansson
2018-05-26 8:37 ` Neil Armstrong
2018-05-28 11:16 ` Viresh Kumar
2018-05-28 11:13 ` Viresh Kumar
2018-06-02 8:14 ` Olof Johansson
2018-06-05 4:37 ` Viresh Kumar
2018-05-25 5:40 ` [PATCH 2/6] arm64: dts: freescale: " Viresh Kumar
2018-07-03 7:34 ` Shawn Guo
2018-07-03 8:34 ` Viresh Kumar
2018-07-03 10:08 ` Shawn Guo [this message]
2018-05-25 5:40 ` [PATCH 3/6] arm64: dts: hisilicon: " Viresh Kumar
2018-05-26 18:00 ` Wei Xu
2018-05-26 18:21 ` Wei Xu
2018-07-18 5:58 ` Viresh Kumar
2018-07-18 15:32 ` Wei Xu
2018-05-25 5:40 ` [PATCH 4/6] arm64: dts: mediatek: " Viresh Kumar
2018-07-02 16:56 ` Matthias Brugger
2018-05-25 5:40 ` [PATCH 5/6] arm64: dts: rockchip: " Viresh Kumar
2018-06-15 11:23 ` Heiko Stübner
2018-05-25 5:40 ` [PATCH 6/6] arm64: dts: socionext: " Viresh Kumar
2018-06-01 3:25 ` Masahiro Yamada
2018-06-04 7:14 ` Viresh Kumar
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=20180703100827.GP4348@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 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).