linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap-gpmc changes for v4.8 merge window
Date: Mon, 4 Jul 2016 22:21:11 -0700	[thread overview]
Message-ID: <20160705052111.GO1669@localhost> (raw)
In-Reply-To: <5770E51B.8040206@ti.com>

On Mon, Jun 27, 2016 at 11:34:35AM +0300, Roger Quadros wrote:
> Hi Arnd/Olof,
> 
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> 
>   Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/rogerq/linux.git gpmc-omap-for-v4.8
> 
> for you to fetch changes up to 32dd625a9f3541ee6d390f12f810f28531d016c7:
> 
>   memory: omap-gpmc: Move gpio functions out of #ifdef CONFIG_OF (2016-06-17 10:26:48 +0300)
> 
> ----------------------------------------------------------------
> OMAP-GPMC: driver updates for v4.8
> 
> * Make GPMC driver non modular as it is going to
> be built-in only till arch/arm/mach-omap2 users
> are removed.
> 
> * Fix build if CONFIG_OF is not defined.

Merged into next/drivers.

> 
> ----------------------------------------------------------------
> Paul Gortmaker (1):
>       memory: omap-gpmc: make it explicitly non-modular
> 
> Roger Quadros (1):
>       memory: omap-gpmc: Move gpio functions out of #ifdef CONFIG_OF
> 
>  drivers/memory/omap-gpmc.c | 136 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------

Tip for the future: If you redirect the output through cat, you get the
diffstat at 80 character lines.


-Olof

  reply	other threads:[~2016-07-05  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  8:34 [GIT PULL] omap-gpmc changes for v4.8 merge window Roger Quadros
2016-07-05  5:21 ` Olof Johansson [this message]
2016-08-01  8:51   ` Roger Quadros

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=20160705052111.GO1669@localhost \
    --to=olof@lixom.net \
    --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).