public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: alexander.stein@systec-electronic.com (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/1] ARM: at91/dt: sam9x5: Add CAN device nodes
Date: Tue, 28 Oct 2014 09:27:15 +0100	[thread overview]
Message-ID: <1963737.sgbgq0RFOC@ws-stein> (raw)
In-Reply-To: <544692A6.9030509@atmel.com>

Hello Nicolas,

On Tuesday 21 October 2014 19:06:46, Nicolas Ferre wrote:
> On 07/10/2014 13:51, Alexander Stein :
> > Add the missing CAN devices node including their pin muxing to the shared
> > .dtsi for at91sam9x5. Actually include this file.
> > While at it, fix white spaces of can1_clk.
> 
> Well, no: I split the patch in two to separate these whitespace
> modifications and the addition of nodes. But now worries, I did it and
> stacked the 2 patches on top of my WIP at91-3.19-dt branch.

It seems this branch is not public, yet. At least I could not find it on git.kernel.org.
Did you also pick "ARM: at91/dt: sam9263: Add CAN device nodes"? (https://www.mail-archive.com/devicetree at vger.kernel.org/msg44970.html)

Best regards,
Alexander
-- 
Dipl.-Inf. Alexander Stein

SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein at systec-electronic.com
Website: www.systec-electronic.com
 
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082

  reply	other threads:[~2014-10-28  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 11:51 [PATCH v4 1/1] ARM: at91/dt: sam9x5: Add CAN device nodes Alexander Stein
2014-10-21 17:06 ` Nicolas Ferre
2014-10-28  8:27   ` Alexander Stein [this message]
2014-11-03 10:32     ` Nicolas Ferre

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=1963737.sgbgq0RFOC@ws-stein \
    --to=alexander.stein@systec-electronic.com \
    --cc=linux-arm-kernel@lists.infradead.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