From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Claudiu.Beznea@microchip.com, Durai.ManickamKR@microchip.com,
Nicolas.Ferre@microchip.com, Cristian.Birsan@microchip.com,
Hari.PrasathGE@microchip.com, davem@davemloft.net,
krzysztof.kozlowski+dt@linaro.org, alexandre.belloni@bootlin.com,
arnd@arndb.de, olof@lixom.net, soc@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Manikandan.M@microchip.com,
Kavyasree.Kotagiri@microchip.com, Horatiu.Vultur@microchip.com
Subject: Re: [PATCHv1 0/8] Add support for sam9x60 curiosity board
Date: Wed, 2 Nov 2022 16:18:21 -0400 [thread overview]
Message-ID: <f984b1b4-c9a5-bbcf-65f2-08e3f231dc96@linaro.org> (raw)
In-Reply-To: <2902eb0e-815a-9147-49e4-182376df378d@microchip.com>
On 31/10/2022 06:20, Claudiu.Beznea@microchip.com wrote:
> On 31.10.2022 05:36, Durai Manickam KR wrote:
>> This patch series addresses the following:
>> - Moving of flexcom definitions from board file to SoC file and
>> some minor changes to its properties.
>> - Add support for the new sam9x60 curiosity board based on the
>> existing sam9x60 SoC.
>>
>> Changes in v1:
>
> This series is actually v2. Also I cannot locate your patches on
> lore.kernel.org don't know why...
>
I was not cced on this submission - I got only reply from yours. As you
pointed out this v1 which is v2 ignores several of my comments.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-02 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221031033653.43269-1-durai.manickamkr@microchip.com>
2022-10-31 10:20 ` [PATCHv1 0/8] Add support for sam9x60 curiosity board Claudiu.Beznea
2022-11-02 20:18 ` Krzysztof Kozlowski [this message]
2022-11-03 5:12 ` Durai.ManickamKR
[not found] ` <20221031033653.43269-2-durai.manickamkr@microchip.com>
2022-10-31 10:22 ` [PATCHv1 1/8] ARM: dts: at91: sam9x60: Fix the label numbering for the flexcom functions Claudiu.Beznea
2022-10-31 10:25 ` Claudiu.Beznea
[not found] ` <20221031033653.43269-3-durai.manickamkr@microchip.com>
2022-10-31 10:23 ` [PATCHv1 2/8] ARM: dts: at91: sam9x60: remove flexcom definitions Claudiu.Beznea
[not found] ` <20221031033653.43269-4-durai.manickamkr@microchip.com>
2022-10-31 10:24 ` [PATCHv1 3/8] ARM: dts: at91: sam9x60: Add " Claudiu.Beznea
2022-10-31 10:27 ` Claudiu.Beznea
2022-11-08 13:37 ` Nicolas Ferre
2022-11-15 5:33 ` Durai.ManickamKR
[not found] ` <20221031033653.43269-7-durai.manickamkr@microchip.com>
2022-10-31 10:28 ` [PATCHv1 6/8] ARM: dts: at91: sam9x60: Add missing " Claudiu.Beznea
2022-11-15 5:40 ` Durai.ManickamKR
[not found] ` <20221031033653.43269-8-durai.manickamkr@microchip.com>
2022-10-31 10:29 ` [PATCHv1 7/8] dt-bindings: arm: at91: Add info on SAM9X60-CURIOSITY Claudiu.Beznea
[not found] ` <20221031033653.43269-9-durai.manickamkr@microchip.com>
2022-10-31 10:29 ` [PATCHv1 8/8] ARM: dts: at91: sam9x60_curiosity: Add device tree for sam9x60_curiosity board Claudiu.Beznea
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=f984b1b4-c9a5-bbcf-65f2-08e3f231dc96@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Durai.ManickamKR@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Manikandan.M@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@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).