From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Brian Norris <computersforpeace@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"arm@kernel.org" <arm@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [GIT PULL] move Versatile flash protection to the device tree
Date: Mon, 25 Apr 2016 23:44:40 +0200 [thread overview]
Message-ID: <6943273.jykU37cR72@wuerfel> (raw)
In-Reply-To: <20160404163626.GA30894@localhost>
On Monday 04 April 2016 09:36:26 Brian Norris wrote:
>
> On Mon, Apr 04, 2016 at 10:45:48AM +0200, Linus Walleij wrote:
> > Hi ARM SoC folks,
> >
> > now I'm tired of waiting for the MTD maintainers' word on this patch
> > series. I sent a question about this approach on february 13:
> > http://marc.info/?l=linux-arm-kernel&m=145537026603174&w=2
> >
> > With subsequent pings on feb 22, mar 5, mar 31, and the cleanup
> > missing the merge window.
> >
> > As you can see the flash protection patch also caters for the
> > RealView flash protection bits.
> >
> > Please pull this into the ARM SoC tree for testing in linux-next
> > for the v4.7 series. If the MTD people appear again and have issues
> > you can always drop the branch.
> >
> >
>
> Acked-by: Brian Norris <computersforpeace@gmail.com>
>
Merged into next/drivers, thanks!
Arnd
prev parent reply other threads:[~2016-04-25 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:45 [GIT PULL] move Versatile flash protection to the device tree Linus Walleij
2016-04-04 16:36 ` Brian Norris
2016-04-25 21:44 ` Arnd Bergmann [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=6943273.jykU37cR72@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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