From: Marc Zyngier <maz@kernel.org>
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix dtbs warnings for arch timer
Date: Wed, 16 Mar 2022 18:47:47 +0000 [thread overview]
Message-ID: <87y219ybsc.wl-maz@kernel.org> (raw)
In-Reply-To: <20220316172051.GA21737@9a2d8922b8f1>
On Wed, 16 Mar 2022 17:20:51 +0000,
Kuldeep Singh <singh.kuldeep87k@gmail.com> wrote:
>
> On Wed, Mar 16, 2022 at 11:27:10AM +0000, Marc Zyngier wrote:
> > On 2022-03-16 09:54, Kuldeep Singh wrote:
> > > This patchset is an attempt to resolve 'make dtbs_check' warning for
> > > arch timer.
> > >
> > > Patch 1 is done in preparation for following patches which defines
> > > compatibles order in more clear way.
> > > Patch 2 documents arm,cortex-a7-timer entry in bindings similar to an
> > > existing entry arm,cortex-a15-timer.
> > > Patch 3 adds above 2 properties in of_match list to bring them in
> > > use.
> > >
> > > Please note, this patchset is based on
> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git, master
> > >
> > > Kuldeep Singh (3):
> > > dt-bindings: timer: Rearrange compatible entries of arch timer
> > > dt-bindings: timer: Document arm,cortex-a7-timer for arch timer
> > > clocksource: arch_timer: Add arm,cortex-a7/15-timer in of_match list
> > >
> > > .../devicetree/bindings/timer/arm,arch_timer.yaml | 13 +++++--------
> > > drivers/clocksource/arm_arch_timer.c | 2 ++
> > > 2 files changed, 7 insertions(+), 8 deletions(-)
> >
> > Please use my @kernel.org address exclusively. My @arm.com
> > address stopped working over two years ago, and the MAINTAINERS
> > file shows the right addresses.
>
> Hi Marc,
>
> I have tocmd and cccmd set in my gitconfig and it generated mail
> addresses automatically so I assume it is correct.
> tocmd ="`pwd`/scripts/get_maintainer.pl --nogit --nogit-fallback --norolestats --nol"
>
> It seems your arm mail address got configured from binding file and not
> from MAINTAINERS.
It is a bug in get_maintainer.pl. You'll have to manually apply the
.mailmap transformation.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-03-16 18:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 9:54 [PATCH 0/3] Fix dtbs warnings for arch timer Kuldeep Singh
2022-03-16 9:54 ` [PATCH 1/3] dt-bindings: timer: Rearrange compatible entries of " Kuldeep Singh
2022-03-16 16:29 ` Krzysztof Kozlowski
2022-03-17 7:02 ` Kuldeep Singh
2022-03-16 9:54 ` [PATCH 2/3] dt-bindings: timer: Document arm,cortex-a7-timer for " Kuldeep Singh
2022-03-16 16:28 ` Krzysztof Kozlowski
2022-03-16 17:43 ` Kuldeep Singh
2022-03-16 9:54 ` [PATCH 3/3] clocksource: arch_timer: Add arm,cortex-a7/15-timer in of_match list Kuldeep Singh
2022-03-16 10:05 ` Marc Zyngier
2022-03-16 16:30 ` Krzysztof Kozlowski
2022-03-16 17:41 ` Kuldeep Singh
2022-03-16 18:43 ` Marc Zyngier
2022-03-17 6:59 ` Kuldeep Singh
2022-03-17 7:18 ` Krzysztof Kozlowski
2022-03-16 11:27 ` [PATCH 0/3] Fix dtbs warnings for arch timer Marc Zyngier
2022-03-16 17:20 ` Kuldeep Singh
2022-03-16 18:47 ` Marc Zyngier [this message]
2022-03-23 19:38 ` Rob Herring
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=87y219ybsc.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=singh.kuldeep87k@gmail.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 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).