From: Lee Jones <lee@kernel.org>
To: Kavyasree.Kotagiri@microchip.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, Nicolas.Ferre@microchip.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v8 0/3] Add support for lan966x flexcom chip-select configuration
Date: Thu, 8 Sep 2022 08:30:56 +0100 [thread overview]
Message-ID: <YxmaMFdprHKMNmr7@google.com> (raw)
In-Reply-To: <CO1PR11MB4865D594CABE612A0FA93CEF92419@CO1PR11MB4865.namprd11.prod.outlook.com>
On Wed, 07 Sep 2022, Kavyasree.Kotagiri@microchip.com wrote:
> >
> > > Hi Lee,
> > >
> > > Are you planning to take this patch series for 6.1 or Can we include them
> > through arm-soc pull-request?
> >
> > I don't seem to have visibility.
> >
> Please find the patches below:
> https://lore.kernel.org/lkml/20220708115619.254073-1-kavyasree.kotagiri@microchip.com/T/
I need patches in my inbox to apply them.
> > Have I Acked it already?
> >
> No.
Then please submit a [RESEND] - with the full Cc list this time.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2022-09-08 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:56 [PATCH v8 0/3] Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-07-08 11:56 ` [PATCH v8 1/3] dt-bindings: mfd: Convert atmel-flexcom to json-schema Kavyasree Kotagiri
2022-07-11 23:05 ` Rob Herring
2022-07-08 11:56 ` [PATCH v8 2/3] dt-bindings: mfd: atmel,sama5d2-flexcom: Add new compatible string for lan966x Kavyasree Kotagiri
2022-07-11 23:06 ` Rob Herring
2022-07-08 11:56 ` [PATCH v8 3/3] mfd: atmel-flexcom: Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-07-12 6:54 ` Claudiu.Beznea
2022-09-05 7:53 ` [PATCH v8 0/3] " Kavyasree.Kotagiri
2022-09-05 14:55 ` Lee Jones
2022-09-07 10:50 ` Kavyasree.Kotagiri
2022-09-08 7:30 ` Lee Jones [this message]
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=YxmaMFdprHKMNmr7@google.com \
--to=lee@kernel.org \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--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=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).