From: Roland Stigge <stigge@antcom.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: Mainlining MTD drivers (lpc32xx)
Date: Mon, 06 Aug 2012 13:21:50 +0200 [thread overview]
Message-ID: <501FA8CE.9040106@antcom.de> (raw)
In-Reply-To: <1344244399.23461.44.camel@shinybook.infradead.org>
On 08/06/2012 11:13 AM, David Woodhouse wrote:
>> during the v3.5-rc phases, I prepared some drivers (lpc32xx_slc and
>> lpc32xx_mlc) which ended up being accepted into l2-mtd and linux-next.
>> Now I realize that they are not in v3.6-rc1.
>>
>> Is there anything I can do at this point? Did anything go wrong or is
>> there a reason for postponing?
>
> No, sorry. This is entirely my fault. I failed to get the pull request
> in to Linus in time for 3.6-rc1. Apologies for that.
Any chance for getting it into a 3.6-rc or needing to wait for 3.7?
Will be fine with any decision, just want to prevent misunderstanding...
Thanks,
Roland
next prev parent reply other threads:[~2012-08-06 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 8:19 Mainlining MTD drivers (lpc32xx) Roland Stigge
2012-08-06 9:13 ` David Woodhouse
2012-08-06 11:21 ` Roland Stigge [this message]
2012-08-15 10:39 ` Artem Bityutskiy
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=501FA8CE.9040106@antcom.de \
--to=stigge@antcom.de \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@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.