All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: yegorslists@googlemail.com
Cc: linux-can@vger.kernel.org, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org, mkl@pengutronix.de,
	andrej.skvortzov@gmail.com,
	Anton Glukhov <anton.a.glukhov@gmail.com>
Subject: Re: [PATCH v5 1/3] ARM: dts: AM35x: Add hecc node
Date: Mon, 6 Mar 2017 08:23:38 -0800	[thread overview]
Message-ID: <20170306162337.GJ20572@atomide.com> (raw)
In-Reply-To: <1487346753-19286-2-git-send-email-yegorslists@googlemail.com>

* yegorslists@googlemail.com <yegorslists@googlemail.com> [170217 07:54]:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> HECC node description for am35x SOCs
> 
> Signed-off-by: Anton Glukhov <anton.a.glukhov@gmail.com>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>

Picking this patch into omap-for-v4.12/dt thanks.

Regards,

Tony

  reply	other threads:[~2017-03-06 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 15:52 [PATCH v5 0/3] Adding DT support for TI HECC module yegorslists
2017-02-17 15:52 ` [PATCH v5 2/3] can: ti_hecc: Add TI HECC DT binding documentation yegorslists
     [not found]   ` <1487346753-19286-3-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-27 16:44     ` Rob Herring
2017-02-28  8:04       ` Marc Kleine-Budde
2017-02-17 15:52 ` [PATCH v5 3/3] can: ti_hecc: Add DT support for TI HECC module yegorslists
     [not found] ` <1487346753-19286-1-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-17 15:52   ` [PATCH v5 1/3] ARM: dts: AM35x: Add hecc node yegorslists-gM/Ye1E23mwN+BqQ9rBEUg
2017-03-06 16:23     ` Tony Lindgren [this message]
2017-02-17 16:04   ` [PATCH v5 0/3] Adding DT support for TI HECC module Marc Kleine-Budde

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=20170306162337.GJ20572@atomide.com \
    --to=tony@atomide.com \
    --cc=andrej.skvortzov@gmail.com \
    --cc=anton.a.glukhov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=yegorslists@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.