linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
	ludovic.desroches@microchip.com, robh+dt@kernel.org,
	corbet@lwn.net, linux@armlinux.org.uk,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	devicetree@vger.kernel.org, UNGLinuxDriver@microchip.com,
	Manohar.Puri@microchip.com
Subject: Re: [PATCH 0/4] Add lan966 documentation and remove lan966x.c file
Date: Mon, 4 Oct 2021 22:58:25 +0200	[thread overview]
Message-ID: <YVtq8Qeb4RbenhTG@piout.net> (raw)
In-Reply-To: <09645199-50af-0373-c5bb-e0d745543e5b@microchip.com>

On 04/10/2021 14:55:29+0200, Nicolas Ferre wrote:
> On 04/10/2021 at 13:09, Alexandre Belloni wrote:
> > On 04/10/2021 16:29:22+0530, Kavyasree Kotagiri wrote:
> > > This patch series modifies Kconfig entry, adds documentation for
> > > lan966 family and removes lan966x setup code file as it is not
> > > required.
> > > 
> > > These patches are generated from at91/linux.git
> > > I had agreement with Nicolas Ferre that he will merge these changes
> > > into existing patch.
> > > 
> > 
> > Seems good to me, for the whole series:
> > Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> 
> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com> for the whole series,
> added to at91-soc and merged with previous patch.
> 
> Please have a look at the resulting tree or at91-next branch for
> double-checking.
> 

That's way better, no code at all is the best code to maintain ;)
Thanks for your efforts Kavya

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

      reply	other threads:[~2021-10-04 21:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 10:59 [PATCH 0/4] Add lan966 documentation and remove lan966x.c file Kavyasree Kotagiri
2021-10-04 10:59 ` [PATCH 1/4] ARM: at91: Kconfig: use only one name SOC_LAN966 and merge options Kavyasree Kotagiri
2021-10-04 10:59 ` [PATCH 2/4] ARM: at91: Documentation: add lan966 family Kavyasree Kotagiri
2021-10-04 10:59 ` [PATCH 3/4] dt-bindings: arm: at91: Document lan966 pcb8291 and pcb8290 boards Kavyasree Kotagiri
2021-10-04 10:59 ` [PATCH 4/4] ARM: at91: remove lan966x file Kavyasree Kotagiri
2021-10-04 11:09 ` [PATCH 0/4] Add lan966 documentation and remove lan966x.c file Alexandre Belloni
2021-10-04 12:55   ` Nicolas Ferre
2021-10-04 20:58     ` Alexandre Belloni [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=YVtq8Qeb4RbenhTG@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=Manohar.Puri@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=ludovic.desroches@microchip.com \
    --cc=nicolas.ferre@microchip.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).