All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Benoit Cousson <bcousson@baylibre.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [GIT PULL] ARM: OMAP: Some more more Device Tree for 3.13
Date: Wed, 23 Oct 2013 03:25:12 -0700	[thread overview]
Message-ID: <20131023102512.GS15154@atomide.com> (raw)
In-Reply-To: <52679B87.5020108@baylibre.com>

* Benoit Cousson <bcousson@baylibre.com> [131023 02:49]:
> Hi Tony,
> 
> Please pull the branch for even more OMAP Device Tree for v3.13 or later.

Thanks, pulling into omap-for-v3.13/dt. Not planning to pull any more
branches for the upcoming merge window FYI everybody.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: Some more more Device Tree for 3.13
Date: Wed, 23 Oct 2013 03:25:12 -0700	[thread overview]
Message-ID: <20131023102512.GS15154@atomide.com> (raw)
In-Reply-To: <52679B87.5020108@baylibre.com>

* Benoit Cousson <bcousson@baylibre.com> [131023 02:49]:
> Hi Tony,
> 
> Please pull the branch for even more OMAP Device Tree for v3.13 or later.

Thanks, pulling into omap-for-v3.13/dt. Not planning to pull any more
branches for the upcoming merge window FYI everybody.

Regards,

Tony

  reply	other threads:[~2013-10-23 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  9:48 [GIT PULL] ARM: OMAP: Some more more Device Tree for 3.13 Benoit Cousson
2013-10-23  9:48 ` Benoit Cousson
2013-10-23 10:25 ` Tony Lindgren [this message]
2013-10-23 10:25   ` 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=20131023102512.GS15154@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.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.