From: david.woodhouse@intel.com (Woodhouse, David)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: SoC fixes for 3.12-rc
Date: Thu, 19 Sep 2013 23:19:19 +0000 [thread overview]
Message-ID: <1379632757.12963.4.camel@shinybook.infradead.org> (raw)
In-Reply-To: <CAN8TOE8j=oosn-5hAdqoTPcuW-sGvDAHd_nK6BZfJpxMwwpisQ@mail.gmail.com>
On Thu, 2013-09-19 at 15:57 -0700, Brian Norris wrote:
> On Thu, Sep 19, 2013 at 2:39 PM, Woodhouse, David
> <david.woodhouse@intel.com> wrote:
> > On Thu, 2013-09-19 at 12:47 -0700, Olof Johansson wrote:
> >>
> >> - A fix for build breakage in the MTD subsystem for some PXA devices.
> >> David Woodhouse has this patch in his for-next branch but has not been
> >> responding to our requests to send it up so here it is.
> >> I should have amended the commit message to describe the build failure for
> >> CONFIG_OF=n setups, but forgot and now it's down in the stack of commits.
> >
> > Thanks for pulling that in. Apologies for the screwup.
>
> Speaking of such process issues: there's an outstanding patch for a
> (small) memory leak that was introduced in the nand_base.c ONFI code
> in 3.12-rc1. Can I expect you to attend to these sort of -rcX (where X
> > 1) issues? Or should I send Linus the patch myself? I don't really
> want it to wait around until 3.13-rc1 to go to -stable.
I'm aware of it, and will get to it shortly. Was going to round it up
along with the one that Olof just sent, either some time this week at
Plumbers or when I get home.
If you want to stick it in the linux-mtd.git tree before that and send
Linus a pull request, I have no objection.
Does that m25p80 'fix 4 byte addressing' fix for Micron not also want to
go in?
--
Sent with MeeGo's ActiveSync support.
David Woodhouse Open Source Technology Centre
David.Woodhouse at intel.com Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4370 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130919/0d2e9c80/attachment-0001.bin>
next prev parent reply other threads:[~2013-09-19 23:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 19:47 [GIT PULL] ARM: SoC fixes for 3.12-rc Olof Johansson
2013-09-19 21:39 ` Woodhouse, David
2013-09-19 22:12 ` Olof Johansson
2013-09-19 22:57 ` Brian Norris
2013-09-19 23:19 ` Woodhouse, David [this message]
2013-09-20 0:44 ` Brian Norris
2013-09-27 10:59 ` Woodhouse, David
2013-09-27 17:40 ` Brian Norris
-- strict thread matches above, loose matches on Subject: below --
2013-10-25 10:21 Olof Johansson
2013-10-13 16:43 Olof Johansson
2013-10-03 4:15 Olof Johansson
2013-09-12 20:01 Olof Johansson
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=1379632757.12963.4.camel@shinybook.infradead.org \
--to=david.woodhouse@intel.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;
as well as URLs for NNTP newsgroup(s).