All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v2 0/5] arm64: dts: meson: g12a: add ethernet support
Date: Mon, 20 May 2019 11:50:27 -0700	[thread overview]
Message-ID: <7hd0kd7yfg.fsf@baylibre.com> (raw)
In-Reply-To: <7himu58195.fsf@baylibre.com>

Kevin Hilman <khilman@baylibre.com> writes:

> Jerome Brunet <jbrunet@baylibre.com> writes:
>
>> Add network support to the g12a SoC family
>>
>> This is series is based on 5.2-rc1 and the patches I already sent last
>> week. If this is not convient for you, please let me know, I'll rebase.
>
> Could you apply this on top of the "consistently order nodes" patches
> that are already in my v5.3/dt64 branch?

Nevermind, I mis-read the above and thought it was on v5.2-rc1, but now
see that it's on -rc1 + all your other series, so it's all good.

Kevin

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

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] arm64: dts: meson: g12a: add ethernet support
Date: Mon, 20 May 2019 11:50:27 -0700	[thread overview]
Message-ID: <7hd0kd7yfg.fsf@baylibre.com> (raw)
In-Reply-To: <7himu58195.fsf@baylibre.com>

Kevin Hilman <khilman@baylibre.com> writes:

> Jerome Brunet <jbrunet@baylibre.com> writes:
>
>> Add network support to the g12a SoC family
>>
>> This is series is based on 5.2-rc1 and the patches I already sent last
>> week. If this is not convient for you, please let me know, I'll rebase.
>
> Could you apply this on top of the "consistently order nodes" patches
> that are already in my v5.3/dt64 branch?

Nevermind, I mis-read the above and thought it was on v5.2-rc1, but now
see that it's on -rc1 + all your other series, so it's all good.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] arm64: dts: meson: g12a: add ethernet support
Date: Mon, 20 May 2019 11:50:27 -0700	[thread overview]
Message-ID: <7hd0kd7yfg.fsf@baylibre.com> (raw)
In-Reply-To: <7himu58195.fsf@baylibre.com>

Kevin Hilman <khilman@baylibre.com> writes:

> Jerome Brunet <jbrunet@baylibre.com> writes:
>
>> Add network support to the g12a SoC family
>>
>> This is series is based on 5.2-rc1 and the patches I already sent last
>> week. If this is not convient for you, please let me know, I'll rebase.
>
> Could you apply this on top of the "consistently order nodes" patches
> that are already in my v5.3/dt64 branch?

Nevermind, I mis-read the above and thought it was on v5.2-rc1, but now
see that it's on -rc1 + all your other series, so it's all good.

Kevin

  reply	other threads:[~2019-05-20 18:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 13:13 [PATCH v2 0/5] arm64: dts: meson: g12a: add ethernet support Jerome Brunet
2019-05-20 13:13 ` Jerome Brunet
2019-05-20 13:13 ` [PATCH v2 1/5] arm64: dts: meson: g12a: add ethernet mac controller Jerome Brunet
2019-05-20 13:13   ` Jerome Brunet
2019-05-20 17:29   ` Martin Blumenstingl
2019-05-20 17:29     ` Martin Blumenstingl
2019-05-20 13:13 ` [PATCH v2 2/5] arm64: dts: meson: g12a: add ethernet pinctrl definitions Jerome Brunet
2019-05-20 13:13   ` Jerome Brunet
2019-05-20 17:29   ` Martin Blumenstingl
2019-05-20 17:29     ` Martin Blumenstingl
2019-05-20 13:13 ` [PATCH v2 3/5] arm64: dts: meson: g12a: add mdio multiplexer Jerome Brunet
2019-05-20 13:13   ` Jerome Brunet
2019-05-20 17:37   ` Martin Blumenstingl
2019-05-20 17:37     ` Martin Blumenstingl
2019-05-20 19:05     ` Andrew Lunn
2019-05-20 19:05       ` Andrew Lunn
2019-05-20 21:51       ` Jerome Brunet
2019-05-20 21:51         ` Jerome Brunet
2019-05-23 17:18         ` Kevin Hilman
2019-05-23 17:18           ` Kevin Hilman
2019-05-20 13:14 ` [PATCH v2 4/5] arm64: dts: meson: u200: add internal network Jerome Brunet
2019-05-20 13:14   ` Jerome Brunet
2019-05-20 17:38   ` Martin Blumenstingl
2019-05-20 17:38     ` Martin Blumenstingl
2019-05-20 13:14 ` [PATCH v2 5/5] arm64: dts: meson: sei510: add network support Jerome Brunet
2019-05-20 13:14   ` Jerome Brunet
2019-05-20 17:38   ` Martin Blumenstingl
2019-05-20 17:38     ` Martin Blumenstingl
2019-05-20 17:49 ` [PATCH v2 0/5] arm64: dts: meson: g12a: add ethernet support Kevin Hilman
2019-05-20 17:49   ` Kevin Hilman
2019-05-20 17:49   ` Kevin Hilman
2019-05-20 18:50   ` Kevin Hilman [this message]
2019-05-20 18:50     ` Kevin Hilman
2019-05-20 18:50     ` Kevin Hilman
2019-05-23 17:20 ` Kevin Hilman
2019-05-23 17:20   ` Kevin Hilman
2019-05-23 17:20   ` Kevin Hilman

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=7hd0kd7yfg.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.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.