public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci fixes for v4.6
Date: Fri, 29 Apr 2016 14:55:02 +0530	[thread overview]
Message-ID: <5723286E.7050601@ti.com> (raw)

Hi,

Sorry for sending this late, but I was waiting to see if
Greg would rather send this (because the issue came
through patches he merged). I have not received a response
and there is danger of missing v4.6 altogether if we wait
any further.

So here it is. Its based on latest in Linus's tree.

Regards,
Sekhar

The following changes since commit 92c19ea9535707701861b7533253a516c7d115c9:

  Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2016-04-28 20:24:27 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-fixes-for-v4.6

for you to fetch changes up to 29b933b6d84219af8456dee172ddc6d676ebbcd3:

  ARM: davinci: only use NVMEM when available (2016-04-29 14:21:14 +0530)

----------------------------------------------------------------
This patch fixes build breakage when
nvmem framework is built as module.

----------------------------------------------------------------
Arnd Bergmann (1):
      ARM: davinci: only use NVMEM when available

 arch/arm/mach-davinci/board-mityomapl138.c | 5 +++++
 arch/arm/mach-davinci/common.c             | 5 +++++
 2 files changed, 10 insertions(+)

             reply	other threads:[~2016-04-29  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  9:25 Sekhar Nori [this message]
2016-04-29 19:02 ` [GIT PULL] DaVinci fixes for v4.6 Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2016-02-23  9:53 Sekhar Nori
2016-02-26 16:48 ` Arnd Bergmann

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=5723286E.7050601@ti.com \
    --to=nsekhar@ti.com \
    --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