public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <palmer@dabbelt.com>, <krzysztof.kozlowski@linaro.org>
Cc: <Conor.Paxton@microchip.com>, <Conor.Dooley@microchip.com>,
	<Lewis.Hanly@microchip.com>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <paul.walmsley@sifive.com>,
	<aou@eecs.berkeley.edu>, <linux-riscv@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv: dts: microchip: fix gpio1 reg property typo
Date: Tue, 17 May 2022 15:58:11 +0000	[thread overview]
Message-ID: <db14be2c-6088-8000-df5f-9dbd5520dd41@microchip.com> (raw)
In-Reply-To: <mhng-3ddeb279-a369-4eef-b74f-5a4597852519@palmer-ri-x1c9>



On 17/05/2022 16:53, Palmer Dabbelt wrote:
> On Tue, 17 May 2022 07:51:32 PDT (-0700), krzysztof.kozlowski@linaro.org wrote:
>> On 17/05/2022 12:40, Conor Paxton wrote:
>>> Fix reg address typo in the gpio1 stanza.
>>>
>>> Signed-off-by: Conor Paxton <conor.paxton@microchip.com>
>>> ---
>>>  arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi | 2 +-
>>
>> Pressed send to fast...
>>
>> Please add Fixes tag, unless fixed commit SHA is not considered stable.
> 
> Conor might be asleep, and as it's late in the cycle I figured I'd just chime in directly.  This LGTM, I usually add fixes myself if there aren't any.  Unless there's any objections to

It's not even 1700 yet, neither Conor on the mail is asleep!

> 
> Fixes: 528a5b1f2556 ("riscv: dts: microchip: add new peripherals to icicle kit device tree")

Saw Krzysztof's mail as I went out the door, I was gonna add an RB & the fixes tag
once I got home but beaten to the punch.
FWIW at this point:

Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

> 
> I'll put this on fixes.
> 
> Thanks!
> 
> 
>>
>>
>> Best regards,
>> Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2022-05-17 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 10:40 [PATCH] riscv: dts: microchip: fix gpio1 reg property typo Conor Paxton
2022-05-17 14:50 ` Krzysztof Kozlowski
2022-05-17 14:51 ` Krzysztof Kozlowski
2022-05-17 15:53   ` Palmer Dabbelt
2022-05-17 15:58     ` Conor.Dooley [this message]

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=db14be2c-6088-8000-df5f-9dbd5520dd41@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Conor.Paxton@microchip.com \
    --cc=Lewis.Hanly@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.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