All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 4/4] omap dt changes for v3.16 merge window, part 2
Date: Mon, 26 May 2014 19:47:41 -0700	[thread overview]
Message-ID: <20140527024741.GA4662@atomide.com> (raw)
In-Reply-To: <20140526200304.GH27093@quad.lixom.net>

* Olof Johansson <olof@lixom.net> [140526 13:03]:
> On Mon, May 19, 2014 at 06:31:25PM -0700, Tony Lindgren wrote:
> > The following changes since commit 3fdb77174a2c173e0e69f2499b836a0e412f6c4d:
> > 
> >   ARM: dts: omap3-n900: use MATRIX_KEY for keymap (2014-05-06 10:22:51 -0700)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.16/dt-part2-v2
> > 
> > for you to fetch changes up to d712ff63b18309c939396f593510fbcccbafb9e4:
> > 
> >   ARM: dts: Enable mcpdm and mcbsp1 on DuoVero (2014-05-19 17:20:31 -0700)
> > 
> > ----------------------------------------------------------------
> > Device tree related changes for omaps.
> 
> Merged into next/dt.
> 
> I'd appreciate a bit more verbose tag messages though -- a very brief
> overview of what's new in here, etc. I think you used to do them in the past?

Just laziness.. I'll have more verbose overview next time.

Thanks,

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 4/4] omap dt changes for v3.16 merge window, part 2
Date: Mon, 26 May 2014 19:47:41 -0700	[thread overview]
Message-ID: <20140527024741.GA4662@atomide.com> (raw)
In-Reply-To: <20140526200304.GH27093@quad.lixom.net>

* Olof Johansson <olof@lixom.net> [140526 13:03]:
> On Mon, May 19, 2014 at 06:31:25PM -0700, Tony Lindgren wrote:
> > The following changes since commit 3fdb77174a2c173e0e69f2499b836a0e412f6c4d:
> > 
> >   ARM: dts: omap3-n900: use MATRIX_KEY for keymap (2014-05-06 10:22:51 -0700)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.16/dt-part2-v2
> > 
> > for you to fetch changes up to d712ff63b18309c939396f593510fbcccbafb9e4:
> > 
> >   ARM: dts: Enable mcpdm and mcbsp1 on DuoVero (2014-05-19 17:20:31 -0700)
> > 
> > ----------------------------------------------------------------
> > Device tree related changes for omaps.
> 
> Merged into next/dt.
> 
> I'd appreciate a bit more verbose tag messages though -- a very brief
> overview of what's new in here, etc. I think you used to do them in the past?

Just laziness.. I'll have more verbose overview next time.

Thanks,

Tony

  reply	other threads:[~2014-05-27  2:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  1:31 [GIT PULL 4/4] omap dt changes for v3.16 merge window, part 2 Tony Lindgren
2014-05-20  1:31 ` Tony Lindgren
2014-05-20  1:55 ` Tony Lindgren
2014-05-20  1:55   ` Tony Lindgren
2014-05-26 20:03 ` Olof Johansson
2014-05-26 20:03   ` Olof Johansson
2014-05-27  2:47   ` Tony Lindgren [this message]
2014-05-27  2:47     ` 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=20140527024741.GA4662@atomide.com \
    --to=tony@atomide.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    /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.