All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	patrikbachan@gmail.com, serge@hallyn.com, bcousson@baylibre.com,
	robh+dt@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] n900 device tree: cleanup
Date: Thu, 5 Jan 2017 08:15:14 -0800	[thread overview]
Message-ID: <20170105161514.GB4310@atomide.com> (raw)
In-Reply-To: <201612141328.27244@pali>

* Pali Rohár <pali.rohar@gmail.com> [161214 04:28]:
> On Wednesday 07 December 2016 04:10:48 Sebastian Reichel wrote:
> > Hi Tony,
> > 
> > It looks like this fell through the cracks. Apart from inconsistent
> > patch subject:
> > 
> > Reviewed-By: Sebastian Reichel <sre@kernel.org>
> 
> Fine for me too. Reviewed-By: Pali Rohár <pali.rohar@gmail.com>

Fixing subject line to use "ARM: dts: n900: cleanup" and applying into
omap-for-v4.11/dt.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] n900 device tree: cleanup
Date: Thu, 5 Jan 2017 08:15:14 -0800	[thread overview]
Message-ID: <20170105161514.GB4310@atomide.com> (raw)
In-Reply-To: <201612141328.27244@pali>

* Pali Roh?r <pali.rohar@gmail.com> [161214 04:28]:
> On Wednesday 07 December 2016 04:10:48 Sebastian Reichel wrote:
> > Hi Tony,
> > 
> > It looks like this fell through the cracks. Apart from inconsistent
> > patch subject:
> > 
> > Reviewed-By: Sebastian Reichel <sre@kernel.org>
> 
> Fine for me too. Reviewed-By: Pali Roh?r <pali.rohar@gmail.com>

Fixing subject line to use "ARM: dts: n900: cleanup" and applying into
omap-for-v4.11/dt.

Tony

  reply	other threads:[~2017-01-05 16:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11  7:54 [PATCH] n900 device tree: cleanup, add camera flash Pavel Machek
2016-10-11  7:54 ` Pavel Machek
2016-10-11  7:54 ` Pavel Machek
2016-10-11  8:01 ` Pali Rohár
2016-10-11  8:01   ` Pali Rohár
2016-10-11  8:10   ` Pavel Machek
2016-10-11  8:10     ` Pavel Machek
2016-10-11  8:10     ` Pavel Machek
2016-10-11  8:12 ` [PATCH] n900 device tree: cleanup Pavel Machek
2016-10-11  8:12   ` Pavel Machek
2016-10-11  8:12   ` Pavel Machek
2016-12-07  3:10   ` Sebastian Reichel
2016-12-07  3:10     ` Sebastian Reichel
2016-12-07  3:10     ` Sebastian Reichel
2016-12-14 12:28     ` Pali Rohár
2016-12-14 12:28       ` Pali Rohár
2016-12-14 12:28       ` Pali Rohár
2017-01-05 16:15       ` Tony Lindgren [this message]
2017-01-05 16:15         ` Tony Lindgren

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=20170105161514.GB4310@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pali.rohar@gmail.com \
    --cc=patrikbachan@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=serge@hallyn.com \
    --cc=sre@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.