All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linus.walleij@linaro.org
Cc: netdev@vger.kernel.org, mirq-linux@rere.qmqm.pl,
	janos.dev@gmail.com, paulius.zaleckas@gmail.com,
	linux-arm-kernel@lists.infradead.org, ulli.kroll@googlemail.com,
	f.fainelli@gmail.com, devicetree@vger.kernel.org,
	tobias.waldvogel@gmail.com
Subject: Re: [PATCH net-next 1/2 v10] net: ethernet: Add DT bindings for the Gemini ethernet
Date: Wed, 10 Jan 2018 15:40:47 -0500 (EST)	[thread overview]
Message-ID: <20180110.154047.2155726732823195708.davem@davemloft.net> (raw)
In-Reply-To: <20180109221053.927-1-linus.walleij@linaro.org>

From: Linus Walleij <linus.walleij@linaro.org>
Date: Tue,  9 Jan 2018 23:10:52 +0100

> This adds the device tree bindings for the Gemini ethernet
> controller. It is pretty straight-forward, using standard
> bindings and modelling the two child ports as child devices
> under the parent ethernet controller device.
> 
> Cc: devicetree@vger.kernel.org
> Cc: Tobias Waldvogel <tobias.waldvogel@gmail.com>
> Cc: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

Applied.

WARNING: multiple messages have this Message-ID (diff)
From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next 1/2 v10] net: ethernet: Add DT bindings for the Gemini ethernet
Date: Wed, 10 Jan 2018 15:40:47 -0500 (EST)	[thread overview]
Message-ID: <20180110.154047.2155726732823195708.davem@davemloft.net> (raw)
In-Reply-To: <20180109221053.927-1-linus.walleij@linaro.org>

From: Linus Walleij <linus.walleij@linaro.org>
Date: Tue,  9 Jan 2018 23:10:52 +0100

> This adds the device tree bindings for the Gemini ethernet
> controller. It is pretty straight-forward, using standard
> bindings and modelling the two child ports as child devices
> under the parent ethernet controller device.
> 
> Cc: devicetree at vger.kernel.org
> Cc: Tobias Waldvogel <tobias.waldvogel@gmail.com>
> Cc: Micha? Miros?aw <mirq-linux@rere.qmqm.pl>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

Applied.

  parent reply	other threads:[~2018-01-10 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 22:10 [PATCH net-next 1/2 v10] net: ethernet: Add DT bindings for the Gemini ethernet Linus Walleij
2018-01-09 22:10 ` Linus Walleij
2018-01-09 22:10 ` [PATCH net-next 2/2 v10] net: ethernet: Add a driver for Gemini gigabit ethernet Linus Walleij
2018-01-10 20:41   ` David Miller
2018-01-10 20:41     ` David Miller
2018-01-10 20:43     ` David Miller
2018-01-10 20:43       ` David Miller
2018-01-10 22:02       ` Linus Walleij
2018-01-10 22:02         ` Linus Walleij
2018-01-10 20:40 ` David Miller [this message]
2018-01-10 20:40   ` [PATCH net-next 1/2 v10] net: ethernet: Add DT bindings for the Gemini ethernet David Miller

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=20180110.154047.2155726732823195708.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=janos.dev@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=netdev@vger.kernel.org \
    --cc=paulius.zaleckas@gmail.com \
    --cc=tobias.waldvogel@gmail.com \
    --cc=ulli.kroll@googlemail.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 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.