All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Simon Horman <horms@verge.net.au>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	devicetree@vger.kernel.org,
	Takeshi Kihara <takeshi.kihara.df@renesas.com>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Rob Herring <robh@kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r8a77965: Add CAN FD controller node
Date: Wed, 21 Nov 2018 00:33:16 +0100	[thread overview]
Message-ID: <f22cb7bc-6aca-b9ed-bd7f-a6c9bae38d4d@gmail.com> (raw)
In-Reply-To: <20181119104419.aznzc6nafwaaxalw@verge.net.au>

On 11/19/2018 11:44 AM, Simon Horman wrote:
> On Mon, Nov 19, 2018 at 12:29:37AM +0100, Marek Vasut wrote:
>> On 11/19/2018 12:10 AM, Wolfram Sang wrote:
>>> On Sun, Nov 18, 2018 at 06:33:27PM +0100, Marek Vasut wrote:
>>>> From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>>>
>>>> This patch adds CAN FD controller nodes for the R8A77965 SoC.
>>>>
>>>> Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>>>> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
>>>> Cc: Rob Herring <robh@kernel.org>
>>>> Cc: Simon Horman <horms+renesas@verge.net.au>
>>>> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>>> Cc: linux-renesas-soc@vger.kernel.org
>>>> Cc: linux-arm-kernel@lists.infradead.org
>>>
>>> Why seperate patches for CAN and CANFD here while they are merged for
>>> r8a77990 into one patch?
>>
>> Because they are two different IP blocks, but I can merge the patches
>> together if that's what you want.
> 
> Merging these patches makes sense to me.

Done

-- 
Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: renesas: r8a77965: Add CAN FD controller node
Date: Wed, 21 Nov 2018 00:33:16 +0100	[thread overview]
Message-ID: <f22cb7bc-6aca-b9ed-bd7f-a6c9bae38d4d@gmail.com> (raw)
In-Reply-To: <20181119104419.aznzc6nafwaaxalw@verge.net.au>

On 11/19/2018 11:44 AM, Simon Horman wrote:
> On Mon, Nov 19, 2018 at 12:29:37AM +0100, Marek Vasut wrote:
>> On 11/19/2018 12:10 AM, Wolfram Sang wrote:
>>> On Sun, Nov 18, 2018 at 06:33:27PM +0100, Marek Vasut wrote:
>>>> From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>>>
>>>> This patch adds CAN FD controller nodes for the R8A77965 SoC.
>>>>
>>>> Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>>>> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
>>>> Cc: Rob Herring <robh@kernel.org>
>>>> Cc: Simon Horman <horms+renesas@verge.net.au>
>>>> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>>> Cc: linux-renesas-soc at vger.kernel.org
>>>> Cc: linux-arm-kernel at lists.infradead.org
>>>
>>> Why seperate patches for CAN and CANFD here while they are merged for
>>> r8a77990 into one patch?
>>
>> Because they are two different IP blocks, but I can merge the patches
>> together if that's what you want.
> 
> Merging these patches makes sense to me.

Done

-- 
Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: Simon Horman <horms@verge.net.au>
Cc: devicetree@vger.kernel.org,
	Takeshi Kihara <takeshi.kihara.df@renesas.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Wolfram Sang <wsa@the-dreams.de>,
	linux-renesas-soc@vger.kernel.org,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Rob Herring <robh@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r8a77965: Add CAN FD controller node
Date: Wed, 21 Nov 2018 00:33:16 +0100	[thread overview]
Message-ID: <f22cb7bc-6aca-b9ed-bd7f-a6c9bae38d4d@gmail.com> (raw)
In-Reply-To: <20181119104419.aznzc6nafwaaxalw@verge.net.au>

On 11/19/2018 11:44 AM, Simon Horman wrote:
> On Mon, Nov 19, 2018 at 12:29:37AM +0100, Marek Vasut wrote:
>> On 11/19/2018 12:10 AM, Wolfram Sang wrote:
>>> On Sun, Nov 18, 2018 at 06:33:27PM +0100, Marek Vasut wrote:
>>>> From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>>>
>>>> This patch adds CAN FD controller nodes for the R8A77965 SoC.
>>>>
>>>> Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>>>> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
>>>> Cc: Rob Herring <robh@kernel.org>
>>>> Cc: Simon Horman <horms+renesas@verge.net.au>
>>>> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>>> Cc: linux-renesas-soc@vger.kernel.org
>>>> Cc: linux-arm-kernel@lists.infradead.org
>>>
>>> Why seperate patches for CAN and CANFD here while they are merged for
>>> r8a77990 into one patch?
>>
>> Because they are two different IP blocks, but I can merge the patches
>> together if that's what you want.
> 
> Merging these patches makes sense to me.

Done

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-11-21 10:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18 17:33 [PATCH 1/2] arm64: dts: renesas: r8a77965: Add CAN controller nodes Marek Vasut
2018-11-18 17:33 ` Marek Vasut
2018-11-18 17:33 ` Marek Vasut
2018-11-18 17:33 ` [PATCH 2/2] arm64: dts: renesas: r8a77965: Add CAN FD controller node Marek Vasut
2018-11-18 17:33   ` Marek Vasut
2018-11-18 17:33   ` Marek Vasut
2018-11-18 23:10   ` Wolfram Sang
2018-11-18 23:10     ` Wolfram Sang
2018-11-18 23:10     ` Wolfram Sang
2018-11-18 23:29     ` Marek Vasut
2018-11-18 23:29       ` Marek Vasut
2018-11-18 23:29       ` Marek Vasut
2018-11-19 10:44       ` Simon Horman
2018-11-19 10:44         ` Simon Horman
2018-11-19 10:44         ` Simon Horman
2018-11-20 23:33         ` Marek Vasut [this message]
2018-11-20 23:33           ` Marek Vasut
2018-11-20 23:33           ` Marek Vasut
2018-11-18 23:02 ` [PATCH 1/2] arm64: dts: renesas: r8a77965: Add CAN controller nodes Wolfram Sang
2018-11-18 23:02   ` Wolfram Sang
2018-11-18 23:02   ` Wolfram Sang
2018-11-18 23:46   ` Marek Vasut
2018-11-18 23:46     ` Marek Vasut
2018-11-18 23:46     ` Marek Vasut
2018-11-19  9:00     ` Geert Uytterhoeven
2018-11-19  9:00       ` Geert Uytterhoeven
2018-11-19  9:00       ` Geert Uytterhoeven
2018-11-20 23:30       ` Marek Vasut
2018-11-20 23:30         ` Marek Vasut
2018-11-20 23:30         ` Marek Vasut
2018-11-21  7:37         ` Geert Uytterhoeven
2018-11-21  7:37           ` Geert Uytterhoeven
2018-11-21  7:37           ` Geert Uytterhoeven
2018-12-05 16:50           ` Marek Vasut
2018-12-05 16:50             ` Marek Vasut
2018-12-05 16:50             ` Marek Vasut

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=f22cb7bc-6aca-b9ed-bd7f-a6c9bae38d4d@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=mkl@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=takeshi.kihara.df@renesas.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.de \
    /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.