From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci fix for v4.10
Date: Thu, 19 Jan 2017 16:23:49 -0800 [thread overview]
Message-ID: <20170120002349.GA32705@localhost> (raw)
In-Reply-To: <dd59ae9d-e224-7fd0-bcaf-856ca1b10b94@ti.com>
On Thu, Jan 19, 2017 at 09:20:55AM +0530, Sekhar Nori wrote:
> Hi Olof,
>
> On Thursday 19 January 2017 05:42 AM, Olof Johansson wrote:
> > Hi Sekhar,
> >
> > On Wed, Jan 18, 2017 at 04:23:55PM +0530, Sekhar Nori wrote:
> >> The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:
> >>
> >> Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)
> >>
> >> 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.10-part2
> >>
> >> for you to fetch changes up to 6f042ee9cc09792c1c0f0cd8f275c2b4b29eaa96:
> >>
> >> ARM: dts: da850-evm: fix read access to SPI flash (2017-01-18 15:38:08 +0530)
> >>
> >> ----------------------------------------------------------------
> >> This patch uses fast-read opcode to read the
> >> SPI flash. This is needed for error-free read
> >> at 30Mhz.
> >>
> >> ----------------------------------------------------------------
> >> Fabien Parent (1):
> >> ARM: dts: da850-evm: fix read access to SPI flash
> >
> > You're ahead of our branch since this is based on -rc4 when it doesn't
> > have to. Want to respin, or should I cherry-pick the patch?
>
> Cherry-picking is fine. Thanks!
Great, cherry-picked to fixes. Please drop from your for-next branch if you
have one.
-Olof
next prev parent reply other threads:[~2017-01-20 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:53 [GIT PULL] DaVinci fix for v4.10 Sekhar Nori
2017-01-18 15:30 ` Sekhar Nori
2017-01-19 0:12 ` Olof Johansson
2017-01-19 3:50 ` Sekhar Nori
2017-01-20 0:23 ` Olof Johansson [this message]
2017-01-20 6:02 ` Sekhar Nori
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=20170120002349.GA32705@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 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.