linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Header Cleanup for v3.17
Date: Mon, 7 Jul 2014 08:30:06 +0200	[thread overview]
Message-ID: <20140707063006.GA28697@verge.net.au> (raw)
In-Reply-To: <20140707000307.GE5539@quad.lixom.net>

On Sun, Jul 06, 2014 at 05:03:07PM -0700, Olof Johansson wrote:
> On Mon, Jun 23, 2014 at 11:24:52AM +0900, Simon Horman wrote:
> > Hi Olof, Hi Kevin, Hi Arnd,
> > 
> > Please consider these Renesas ARM based SoC header cleanup for v3.17.
> > 
> > 
> > The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
> > 
> >   Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git renesas-header-cleanup-for-v3.17
> > 
> > for you to fetch changes up to 62872989bdbf1245d7239b9f4c05a8ee7c775ed5:
> > 
> >   ARM: shmobile: Move rcar-gen2.h, cleanup r8a7790 case (2014-06-17 17:09:40 +0900)
> > 
> > ----------------------------------------------------------------
> > Renesas ARM Based SoC Header Cleanup for v3.17
> > 
> > Move the most common shared header files for mach-shmobile
> > from <mach/foobar.h> to "foobar.h"
> > 
> > 6287298 ARM: shmobile: Move rcar-gen2.h, cleanup r8a7790 case
> > 585c09d ARM: shmobile: Move pm-rcar.h, cleanup r8a7779 case
> > 6b8b0cb ARM: shmobile: Move pm-rmobile.h, cleanup sh73xx.h
> > fd44aa5 ARM: shmobile: Move common.h
> > b6bab12 ARM: shmobile: Move most of irqs.h, keep some for pinctl
> > ad6ffa0 ARM: shmobile: Move clock.h
> > 74ac0de ARM: shmobile: Move dma-register.h
> > 6200e2c ARM: shmobile: Move intc.h, cleanup sh_intc.h usage
> 
> Listing the patches and the SHAs in the tag description makes no sense.

Thanks, sorry for letting that slip in.

> (Merged into next/cleanup after taking out the above).
> 
> 
> -Olof
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2014-07-07  6:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23  2:24 [GIT PULL] Renesas ARM Based SoC Header Cleanup for v3.17 Simon Horman
2014-06-23  2:24 ` [PATCH 1/8] ARM: shmobile: Move intc.h, cleanup sh_intc.h usage Simon Horman
2014-06-23  2:24 ` [PATCH 2/8] ARM: shmobile: Move dma-register.h Simon Horman
2014-06-23  2:24 ` [PATCH 3/8] ARM: shmobile: Move clock.h Simon Horman
2014-06-23  2:25 ` [PATCH 4/8] ARM: shmobile: Move most of irqs.h, keep some for pinctl Simon Horman
2014-06-23  2:25 ` [PATCH 5/8] ARM: shmobile: Move common.h Simon Horman
2014-06-23  2:25 ` [PATCH 6/8] ARM: shmobile: Move pm-rmobile.h, cleanup sh73xx.h Simon Horman
2014-06-23  2:25 ` [PATCH 7/8] ARM: shmobile: Move pm-rcar.h, cleanup r8a7779 case Simon Horman
2014-06-23  2:25 ` [PATCH 8/8] ARM: shmobile: Move rcar-gen2.h, cleanup r8a7790 case Simon Horman
2014-07-07  0:03 ` [GIT PULL] Renesas ARM Based SoC Header Cleanup for v3.17 Olof Johansson
2014-07-07  6:30   ` Simon Horman [this message]

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=20140707063006.GA28697@verge.net.au \
    --to=horms@verge.net.au \
    --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;
as well as URLs for NNTP newsgroup(s).