From: Lee Jones <lee.jones@linaro.org>
To: computersforpeace@gmail.com
Cc: angus.clark@st.com, dwmw2@infradead.org,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@stlinux.com
Subject: New NAND driver
Date: Mon, 24 Mar 2014 13:24:46 +0000 [thread overview]
Message-ID: <20140324132446.GA21665@lee--X1> (raw)
Hi Brian,
Firstly I'd like to thank you for supporting the inclusion of ST's SPI
NOR (FSM) driver. As promised I will convert it over to the new
framework once it has been applied by your good self.
In the meantime however, I have a NAND driver which I need to
submit. I wanted to give you a heads-up prior to sending it in case
you had any special requests. FYI: Shoving it where the sun don't
shine, is not a valid request by the way :). It's 2700 lines and I've
split it over 47 patches for reviewing purposes.
Sorry to do this to you Brian, I am sensitive to how over-burdened you
are with the subsystem already. Perhaps it might make sense to put out
a plea for volunteers to help with maintain MTD subsystem on LKML?
Anyway, what's the best thing to do in this instance? Should I just
send it to the list as an RFC and be done with it?
Kind regards,
Lee
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: computersforpeace@gmail.com
Cc: linux-mtd@lists.infradead.org, angus.clark@st.com,
linux-kernel@vger.kernel.org, dwmw2@infradead.org,
kernel@stlinux.com
Subject: New NAND driver
Date: Mon, 24 Mar 2014 13:24:46 +0000 [thread overview]
Message-ID: <20140324132446.GA21665@lee--X1> (raw)
Hi Brian,
Firstly I'd like to thank you for supporting the inclusion of ST's SPI
NOR (FSM) driver. As promised I will convert it over to the new
framework once it has been applied by your good self.
In the meantime however, I have a NAND driver which I need to
submit. I wanted to give you a heads-up prior to sending it in case
you had any special requests. FYI: Shoving it where the sun don't
shine, is not a valid request by the way :). It's 2700 lines and I've
split it over 47 patches for reviewing purposes.
Sorry to do this to you Brian, I am sensitive to how over-burdened you
are with the subsystem already. Perhaps it might make sense to put out
a plea for volunteers to help with maintain MTD subsystem on LKML?
Anyway, what's the best thing to do in this instance? Should I just
send it to the list as an RFC and be done with it?
Kind regards,
Lee
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next reply other threads:[~2014-03-24 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 13:24 Lee Jones [this message]
2014-03-24 13:24 ` New NAND driver Lee Jones
2014-03-24 20:39 ` Marek Vasut
2014-03-24 20:39 ` Marek Vasut
2014-03-25 6:18 ` Gupta, Pekon
2014-03-25 6:18 ` Gupta, Pekon
2014-03-25 7:59 ` Lee Jones
2014-03-25 7:59 ` Lee Jones
2014-03-25 9:49 ` Gupta, Pekon
2014-03-25 9:49 ` Gupta, Pekon
2014-03-25 10:46 ` Lee Jones
2014-03-25 10:46 ` Lee Jones
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=20140324132446.GA21665@lee--X1 \
--to=lee.jones@linaro.org \
--cc=angus.clark@st.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kernel@stlinux.com \
--cc=linux-kernel@vger.kernel.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.