All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"Vivek Unune" <npcomplete13@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	Rob Herring <robh+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: BCM5301X: pinctrl - use correct driver and define mdio pins
Date: Mon, 9 Nov 2020 09:25:02 -0800	[thread overview]
Message-ID: <78b0ca0b-222c-f0bc-9501-98a6bb73e48e@gmail.com> (raw)
In-Reply-To: <CACna6ryJ70PepwE1u-kUqjKWbae6F=Gp2Scoe2pHtaGuJvqacA@mail.gmail.com>

On 11/9/20 9:21 AM, Rafał Miłecki wrote:
> On Wed, 4 Nov 2020 at 21:30, Vivek Unune <npcomplete13@gmail.com> wrote:
>> BCM47094 version of pinmux uses different driver and supports mdio
>> pinmux pins. Hence, use the correct driver and define the pins.
>>
>> Signed-off-by: Vivek Unune <npcomplete13@gmail.com>
> 
> Subject and message are a bit confusing as it's actually a matter of
> chipset specific binding and not a driver.
> 
> Change looks OK, thanks for handling that!
> 
> Acked-by: Rafał Miłecki <rafal@milecki.pl>
> 

Agreed, applied and fixed up the subject and commit message this way:

    ARM: dts: BCM5301X: Use corretc pinctrl compatible for 4709x

    BCM47094 version of pinmux uses different compatible and supports MDIO
    pinmux pins. Hence, use the correct compatible string and defines the
    MDIO pins group.

Thanks!
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"Vivek Unune" <npcomplete13@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>, Hauke Mehrtens <hauke@hauke-m.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: BCM5301X: pinctrl - use correct driver and define mdio pins
Date: Mon, 9 Nov 2020 09:25:02 -0800	[thread overview]
Message-ID: <78b0ca0b-222c-f0bc-9501-98a6bb73e48e@gmail.com> (raw)
In-Reply-To: <CACna6ryJ70PepwE1u-kUqjKWbae6F=Gp2Scoe2pHtaGuJvqacA@mail.gmail.com>

On 11/9/20 9:21 AM, Rafał Miłecki wrote:
> On Wed, 4 Nov 2020 at 21:30, Vivek Unune <npcomplete13@gmail.com> wrote:
>> BCM47094 version of pinmux uses different driver and supports mdio
>> pinmux pins. Hence, use the correct driver and define the pins.
>>
>> Signed-off-by: Vivek Unune <npcomplete13@gmail.com>
> 
> Subject and message are a bit confusing as it's actually a matter of
> chipset specific binding and not a driver.
> 
> Change looks OK, thanks for handling that!
> 
> Acked-by: Rafał Miłecki <rafal@milecki.pl>
> 

Agreed, applied and fixed up the subject and commit message this way:

    ARM: dts: BCM5301X: Use corretc pinctrl compatible for 4709x

    BCM47094 version of pinmux uses different compatible and supports MDIO
    pinmux pins. Hence, use the correct compatible string and defines the
    MDIO pins group.

Thanks!
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-09 17:25 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 19:01 [PATCH 0/3] ARM: dts: BCM5301X: Linksys EA9500 device tree changes Vivek Unune
2020-10-07 19:01 ` Vivek Unune
2020-10-07 19:01 ` [PATCH 1/3] ARM: dts: BCM5301X: Linksys EA9500 make use of pinctrl Vivek Unune
2020-10-07 19:01   ` Vivek Unune
2020-10-07 21:01   ` Andrew Lunn
2020-10-07 21:01     ` Andrew Lunn
2020-10-07 21:46     ` Vivek Unune
2020-10-07 21:46       ` Vivek Unune
2020-10-08  0:26       ` Andrew Lunn
2020-10-08  0:26         ` Andrew Lunn
2020-10-08 12:41         ` Vivek Unune
2020-10-08 12:41           ` Vivek Unune
2020-11-04 20:29   ` [PATCH v2 0/2] " Vivek Unune
2020-11-04 20:29     ` Vivek Unune
2020-11-04 20:29     ` [PATCH v2 1/2] ARM: dts: BCM5301X: pinctrl - use correct driver and define mdio pins Vivek Unune
2020-11-04 20:29       ` Vivek Unune
2020-11-09 17:21       ` Rafał Miłecki
2020-11-09 17:21         ` Rafał Miłecki
2020-11-09 17:25         ` Florian Fainelli [this message]
2020-11-09 17:25           ` Florian Fainelli
2020-11-04 20:29     ` [PATCH v2 2/2] ARM: dts: BCM5301X: Linksys EA9500 make use of pinctrl Vivek Unune
2020-11-04 20:29       ` Vivek Unune
2020-11-04 20:37       ` Florian Fainelli
2020-11-04 20:37         ` Florian Fainelli
2020-11-04 20:58         ` Vivek Unune
2020-11-04 20:58           ` Vivek Unune
2020-11-09 13:24           ` Vivek Unune
2020-11-09 13:24             ` Vivek Unune
2020-11-09 15:54             ` Florian Fainelli
2020-11-09 15:54               ` Florian Fainelli
2020-11-09 17:24       ` Florian Fainelli
2020-11-09 17:24         ` Florian Fainelli
2020-11-10 13:17         ` Vivek Unune
2020-11-10 13:17           ` Vivek Unune
2020-10-07 19:01 ` [PATCH 2/3] ARM: dts: BCM5301X: Linksys EA9500 add port 5 and port 7 Vivek Unune
2020-10-07 19:01   ` Vivek Unune
2020-10-07 21:03   ` Andrew Lunn
2020-10-07 21:03     ` Andrew Lunn
2020-10-07 22:07     ` Vivek Unune
2020-10-07 22:07       ` Vivek Unune
2020-10-08  0:32       ` Andrew Lunn
2020-10-08  0:32         ` Andrew Lunn
2020-10-08 14:58         ` Florian Fainelli
2020-10-08 14:58           ` Florian Fainelli
2020-10-08 20:20           ` Vivek Unune
2020-10-08 20:20             ` Vivek Unune
2020-10-07 19:01 ` [PATCH 3/3] ARM: dts: BCM5301X: Linksys EA9500 add fixed partitions Vivek Unune
2020-10-07 19:01   ` Vivek Unune

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=78b0ca0b-222c-f0bc-9501-98a6bb73e48e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npcomplete13@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=zajec5@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 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.