public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	devicetree <devicetree@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: marvell: Clean up armada-3720-db
Date: Fri, 25 Mar 2016 09:16:04 +0100	[thread overview]
Message-ID: <87oaa3m0qj.fsf@free-electrons.com> (raw)
In-Reply-To: <56F419CA.9010400@suse.de> ("Andreas Färber"'s message of "Thu, 24 Mar 2016 17:46:02 +0100")

Hi Andreas,
 
 On jeu., mars 24 2016, Andreas Färber <afaerber@suse.de> wrote:

> Hi Gregory,
>
> Am 24.03.2016 um 17:11 schrieb Gregory CLEMENT:
>>> +/*
>>> + * Exported on the micro USB connector CON32
>>> + * through an FTDI
>>> + */
>> 
>> As the comment didn't start anymore from the middle of the line, we
>> could have it an a single line. We don't have to split in 2 lines.
>
> Sure. Should I change that along with 4/4 in a v2? It'll be after the
> Easter holidays.

Yes please and no problem for wiating for after the Easter holidays I
won't apply the patch on the mvebu branches before the release of the
v4.6-rc1.

Thanks,

Gregory

>
> Regards,
> Andreas
>
> -- 
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2016-03-25  8:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1458771861-12392-1-git-send-email-afaerber@suse.de>
2016-03-23 22:24 ` [PATCH 1/4] arm64: dts: marvell: Clean up armada-3720-db Andreas Färber
2016-03-24 16:11   ` Gregory CLEMENT
2016-03-24 16:46     ` Andreas Färber
2016-03-25  8:16       ` Gregory CLEMENT [this message]
2016-04-07 19:00         ` Gregory CLEMENT
2016-03-23 22:24 ` [PATCH 2/4] arm64: dts: marvell: Rename armada-37xx USB node Andreas Färber
2016-03-23 22:24 ` [PATCH 3/4] arm64: dts: marvell: Clean up armada-7040-db Andreas Färber
2016-03-24  8:18   ` Thomas Petazzoni
2016-03-24 10:27     ` Gregory CLEMENT
2016-03-24 10:40       ` Thomas Petazzoni
2016-03-24 13:37         ` Andrew Lunn
2016-03-24 13:59           ` Jason Cooper
2016-03-23 22:24 ` [PATCH 4/4] arm64: dts: marvell: Rename armada-ap806 XOR nodes Andreas Färber
2016-03-24  8:17   ` Thomas Petazzoni

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=87oaa3m0qj.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=afaerber@suse.de \
    --cc=andrew@lunn.ch \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox