All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Kavyasree.Kotagiri@microchip.com>
To: <krzysztof.kozlowski@linaro.org>
Cc: <Nicolas.Ferre@microchip.com>, <robh+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<UNGLinuxDriver@microchip.com>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<Claudiu.Beznea@microchip.com>, <lee@kernel.org>
Subject: RE: [RESEND PATCH v9 2/3] dt-bindings: mfd: atmel,sama5d2-flexcom: Add new compatible string for lan966x
Date: Fri, 9 Sep 2022 06:26:44 +0000	[thread overview]
Message-ID: <SA2PR11MB48747201C297AD41A0798DA392439@SA2PR11MB4874.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b25cc1d4-a2a4-efc1-eee8-70459d28311b@linaro.org>



> 
> On 08/09/2022 17:06, Kavyasree Kotagiri wrote:
> > LAN966x SoC flexcoms has two optional I/O lines. Namely, CS0 and CS1
> > in flexcom SPI mode. CTS and RTS in flexcom USART mode. These pins
> > can be mapped to lan966x FLEXCOM_SHARED[0-20] pins and usage
> depends on
> > functions being configured.
> >
> > Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
> 
> Please add Acked-by/Reviewed-by tags when posting new versions.
> However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
> 
> https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/subm
> itting-patches.rst#L540
> 
> If a tag was not added on purpose, please state why and what changed.
> 
Yes, You are right.
I missed adding reviewed-by tag for 2/3 and 3/3 patches(which doesn't have any issues
while applying on latest version)
I haven't added tag for patch-1/3 as there is small change
(i.e., Changed reference provided for spi bindings to atmel,at91rm9200-spi.yaml)
while applying changes on latest version.
> 
> Best regards,
> Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: <Kavyasree.Kotagiri@microchip.com>
To: <krzysztof.kozlowski@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	lee@kernel.org, UNGLinuxDriver@microchip.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, Claudiu.Beznea@microchip.com,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [RESEND PATCH v9 2/3] dt-bindings: mfd: atmel,sama5d2-flexcom: Add new compatible string for lan966x
Date: Fri, 9 Sep 2022 06:26:44 +0000	[thread overview]
Message-ID: <SA2PR11MB48747201C297AD41A0798DA392439@SA2PR11MB4874.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b25cc1d4-a2a4-efc1-eee8-70459d28311b@linaro.org>



> 
> On 08/09/2022 17:06, Kavyasree Kotagiri wrote:
> > LAN966x SoC flexcoms has two optional I/O lines. Namely, CS0 and CS1
> > in flexcom SPI mode. CTS and RTS in flexcom USART mode. These pins
> > can be mapped to lan966x FLEXCOM_SHARED[0-20] pins and usage
> depends on
> > functions being configured.
> >
> > Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
> 
> Please add Acked-by/Reviewed-by tags when posting new versions.
> However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
> 
> https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/subm
> itting-patches.rst#L540
> 
> If a tag was not added on purpose, please state why and what changed.
> 
Yes, You are right.
I missed adding reviewed-by tag for 2/3 and 3/3 patches(which doesn't have any issues
while applying on latest version)
I haven't added tag for patch-1/3 as there is small change
(i.e., Changed reference provided for spi bindings to atmel,at91rm9200-spi.yaml)
while applying changes on latest version.
> 
> Best regards,
> Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-09  6:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 15:06 [RESEND PATCH v9 0/3] Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-09-08 15:06 ` Kavyasree Kotagiri
2022-09-08 15:06 ` [RESEND PATCH v9 1/3] dt-bindings: mfd: Convert atmel-flexcom to json-schema Kavyasree Kotagiri
2022-09-08 15:06   ` Kavyasree Kotagiri
2022-09-08 15:13   ` Krzysztof Kozlowski
2022-09-08 15:13     ` Krzysztof Kozlowski
2022-09-08 21:16   ` Rob Herring
2022-09-08 21:16     ` Rob Herring
2022-09-09  6:18     ` Kavyasree.Kotagiri
2022-09-09  6:18       ` Kavyasree.Kotagiri
2022-09-12  8:16       ` Kavyasree.Kotagiri
2022-09-12  8:16         ` Kavyasree.Kotagiri
2022-09-12 11:03         ` Krzysztof Kozlowski
2022-09-12 11:03           ` Krzysztof Kozlowski
2022-09-13  5:29           ` Kavyasree.Kotagiri
2022-09-13  5:29             ` Kavyasree.Kotagiri
2022-09-13  9:15             ` Krzysztof Kozlowski
2022-09-13  9:15               ` Krzysztof Kozlowski
2022-09-13 10:16               ` Kavyasree.Kotagiri
2022-09-13 10:16                 ` Kavyasree.Kotagiri
2022-09-14  4:56                 ` Kavyasree.Kotagiri
2022-09-14  4:56                   ` Kavyasree.Kotagiri
2022-09-08 15:06 ` [RESEND PATCH v9 2/3] dt-bindings: mfd: atmel,sama5d2-flexcom: Add new compatible string for lan966x Kavyasree Kotagiri
2022-09-08 15:06   ` Kavyasree Kotagiri
2022-09-08 15:14   ` Krzysztof Kozlowski
2022-09-08 15:14     ` Krzysztof Kozlowski
2022-09-09  6:26     ` Kavyasree.Kotagiri [this message]
2022-09-09  6:26       ` Kavyasree.Kotagiri
2022-09-08 15:06 ` [RESEND PATCH v9 3/3] mfd: atmel-flexcom: Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-09-08 15:06   ` Kavyasree Kotagiri
2022-09-08 15:21   ` Kavyasree.Kotagiri
2022-09-08 15:21     ` Kavyasree.Kotagiri
2022-09-15  9:11 ` [RESEND PATCH v9 0/3] " Kavyasree.Kotagiri
2022-09-15  9:11   ` Kavyasree.Kotagiri

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=SA2PR11MB48747201C297AD41A0798DA392439@SA2PR11MB4874.namprd11.prod.outlook.com \
    --to=kavyasree.kotagiri@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.