From: Anand Moon <linux.amoon@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kukjin Kim <kgene@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: exynos5: add missing interrupts for pwm node
Date: Wed, 18 Jul 2018 16:20:28 +0530 [thread overview]
Message-ID: <CANAwSgSaU1kTW3j0OZGwmOWo=p2uHFP8toLUe9FHYEkCJsuLFg@mail.gmail.com> (raw)
In-Reply-To: <CAJKOXPez6cuLyrxBkAKtyx2xiqG7VLWFCBYXkBX_537A=bDpsg@mail.gmail.com>
Hi Krzysztof,
On 18 July 2018 at 16:03, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On 18 July 2018 at 12:30, Anand Moon <linux.amoon@gmail.com> wrote:
>> Hi
>>
>> On 18 July 2018 at 15:27, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>> On 18 July 2018 at 11:34, Anand Moon <linux.amoon@gmail.com> wrote:
>>>> Add missing GIC interrupts property for pwm nodes.
>>>>
>>>> Signed-off-by: Anand Moon <linux.amoon@gmail.com>
>>>> ---
>>>> arch/arm/boot/dts/exynos5.dtsi | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>>>>
>>>> diff --git a/arch/arm/boot/dts/exynos5.dtsi b/arch/arm/boot/dts/exynos5.dtsi
>>>> index 5d2f0a0..9406108 100644
>>>> --- a/arch/arm/boot/dts/exynos5.dtsi
>>>> +++ b/arch/arm/boot/dts/exynos5.dtsi
>>>> @@ -169,6 +169,11 @@
>>>> pwm: pwm@12dd0000 {
>>>> compatible = "samsung,exynos4210-pwm";
>>>> reg = <0x12DD0000 0x100>;
>>>> + interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>,
>>>> + <GIC_SPI 37 IRQ_TYPE_LEVEL_HIGH>,
>>>
>>> Indentation here looks weird - spaces used after tabs but not aligned
>>> with first entry. Please indent it properly and align it.
>>>
>>> Best regards,
>>> Krzysztof
>>
>> I ram checkpatch before I submit this patch it shown no error.
>>
>> # scripts/checkpatch.pl --no-signoff -q
>> 0001-ARM-dts-exynos5-add-missing-interrupts-for-pwm-node.patch
>
> That's good, thank you. Still when I look at it in patchwork the
> indentation is wrong:
> https://patchwork.kernel.org/patch/10531753/
> However it can be patchwork's fault, so are you sure that this is
> properly indented and aligned?
>
> BR,
> Krzysztof
I prefer vim and I use following plugin
https://github.com/vivien/vim-linux-coding-style
root@odroidxu4:/usr/src/odroidxu4-4kr-devel# wget -nv
https://patchwork.kernel.org/patch/10531753/mbox/ -O pwm.patch
2018-07-18 10:48:09
URL:https://patchwork.kernel.org/patch/10531753/mbox/ [1460] ->
"pwm.patch" [1]
root@odroidxu4:/usr/src/odroidxu4-4kr-devel#
root@odroidxu4:/usr/src/odroidxu4-4kr-devel# scripts/checkpatch.pl
--no-signoff -q pwm.patch
root@odroidxu4:/usr/src/odroidxu4-4kr-devel#
Is their any other way to test checkpatch please let me know.
Best Regards
-Anand
next prev parent reply other threads:[~2018-07-18 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 9:34 [PATCH] ARM: dts: exynos5: add missing interrupts for pwm node Anand Moon
2018-07-18 9:57 ` Krzysztof Kozlowski
2018-07-18 10:30 ` Anand Moon
2018-07-18 10:33 ` Krzysztof Kozlowski
2018-07-18 10:50 ` Anand Moon [this message]
2018-07-18 11:55 ` Krzysztof Kozlowski
2018-07-18 13:04 ` Anand Moon
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='CANAwSgSaU1kTW3j0OZGwmOWo=p2uHFP8toLUe9FHYEkCJsuLFg@mail.gmail.com' \
--to=linux.amoon@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).