From: E Shattow <e@freeshell.de>
To: Hal Feng <hal.feng@starfivetech.com>,
Conor Dooley <conor@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jianlong Huang <jianlong.huang@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv: dts: starfive: jh7110-pinfunc.h
Date: Mon, 9 Dec 2024 20:09:23 -0800 [thread overview]
Message-ID: <0f707918-49ce-4f04-b8d4-e74462caff5d@freeshell.de> (raw)
In-Reply-To: <ZQ2PR01MB1307099548C99CD6650BD57CE63DA@ZQ2PR01MB1307.CHNPR01.prod.partner.outlook.cn>
On 12/9/24 18:14, Hal Feng wrote:
>> On 10.12.24 09:49, E Shattow wrote:
>> [PATCH] riscv: dts: starfive: jh7110-pinfunc.h
>
> Describe something in the commit title?
>
>>
>> Fix a typo in StarFive JH7110 pin function definitions
>>
>> Fixes: e22f09e598d12 ("riscv: dts: starfive: Add StarFive JH7110 pin function
>> definitions")
>> Signed-off-by: E Shattow <e@freeshell.de>
>
> Acked-by: Hal Feng <hal.feng@starfivetech.com>
>
> Best regards,
> Hal
>
>> ---
>> arch/riscv/boot/dts/starfive/jh7110-pinfunc.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> b/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> index 256de17f5261..ae49c908e7fb 100644
>> --- a/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> +++ b/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> @@ -89,7 +89,7 @@
>> #define GPOUT_SYS_SDIO1_DATA1 59
>> #define GPOUT_SYS_SDIO1_DATA2 60
>> #define GPOUT_SYS_SDIO1_DATA3 61
>> -#define GPOUT_SYS_SDIO1_DATA4 63
>> +#define GPOUT_SYS_SDIO1_DATA4 62
>> #define GPOUT_SYS_SDIO1_DATA5 63
>> #define GPOUT_SYS_SDIO1_DATA6 64
>> #define GPOUT_SYS_SDIO1_DATA7 65
>>
>> base-commit: 708d55db3edbe2ccf88d94b5f2e2b404bc0ba37c
>> --
>> 2.45.2
>
Ah... yes I forgot the commit title. Will re-send. Thanks! -E
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: E Shattow <e@freeshell.de>
To: Hal Feng <hal.feng@starfivetech.com>,
Conor Dooley <conor@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jianlong Huang <jianlong.huang@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv: dts: starfive: jh7110-pinfunc.h
Date: Mon, 9 Dec 2024 20:09:23 -0800 [thread overview]
Message-ID: <0f707918-49ce-4f04-b8d4-e74462caff5d@freeshell.de> (raw)
In-Reply-To: <ZQ2PR01MB1307099548C99CD6650BD57CE63DA@ZQ2PR01MB1307.CHNPR01.prod.partner.outlook.cn>
On 12/9/24 18:14, Hal Feng wrote:
>> On 10.12.24 09:49, E Shattow wrote:
>> [PATCH] riscv: dts: starfive: jh7110-pinfunc.h
>
> Describe something in the commit title?
>
>>
>> Fix a typo in StarFive JH7110 pin function definitions
>>
>> Fixes: e22f09e598d12 ("riscv: dts: starfive: Add StarFive JH7110 pin function
>> definitions")
>> Signed-off-by: E Shattow <e@freeshell.de>
>
> Acked-by: Hal Feng <hal.feng@starfivetech.com>
>
> Best regards,
> Hal
>
>> ---
>> arch/riscv/boot/dts/starfive/jh7110-pinfunc.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> b/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> index 256de17f5261..ae49c908e7fb 100644
>> --- a/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> +++ b/arch/riscv/boot/dts/starfive/jh7110-pinfunc.h
>> @@ -89,7 +89,7 @@
>> #define GPOUT_SYS_SDIO1_DATA1 59
>> #define GPOUT_SYS_SDIO1_DATA2 60
>> #define GPOUT_SYS_SDIO1_DATA3 61
>> -#define GPOUT_SYS_SDIO1_DATA4 63
>> +#define GPOUT_SYS_SDIO1_DATA4 62
>> #define GPOUT_SYS_SDIO1_DATA5 63
>> #define GPOUT_SYS_SDIO1_DATA6 64
>> #define GPOUT_SYS_SDIO1_DATA7 65
>>
>> base-commit: 708d55db3edbe2ccf88d94b5f2e2b404bc0ba37c
>> --
>> 2.45.2
>
Ah... yes I forgot the commit title. Will re-send. Thanks! -E
next prev parent reply other threads:[~2024-12-10 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 1:48 [PATCH] riscv: dts: starfive: jh7110-pinfunc.h E Shattow
2024-12-10 1:48 ` E Shattow
2024-12-10 2:14 ` Hal Feng
2024-12-10 2:14 ` Hal Feng
2024-12-10 4:09 ` E Shattow [this message]
2024-12-10 4:09 ` E Shattow
2024-12-13 9:36 ` Krzysztof Kozlowski
2024-12-13 9:36 ` Krzysztof Kozlowski
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=0f707918-49ce-4f04-b8d4-e74462caff5d@freeshell.de \
--to=e@freeshell.de \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=jianlong.huang@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@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 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.