From: Lee Jones <lee.jones@linaro.org>
To: pekon@ti.com, ezequiel.garcia@free-electrons.com,
computersforpeace@gmail.com, jgunthorpe@obsidianresearch.com
Cc: angus.clark@st.com, linux-mtd@lists.infradead.org
Subject: ST NAND BCH Driver
Date: Wed, 26 Mar 2014 09:32:35 +0000 [thread overview]
Message-ID: <20140326093235.GH24823@lee--X1> (raw)
Guys,
Firstly I wanted to thank all of your for your responses. I will get
round to answering them and/or fixing-up the code with your great
advice.
Secondly I just wanted to explain my slowness in replying, as I feel
rude just letting your messages sit in my inbox without reply. I'm
currently working on updating ST's (FSM) NOR driver with recent
internal developments. Once complete and submitted I'll turn my hand
to the NAND driver where you'll receive answer to your queries.
Thanks again and keep the suggestions coming. I am reading all of them
and will endeavour to utilise them on next submission.
Kind regards,
Lee
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
reply other threads:[~2014-03-26 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140326093235.GH24823@lee--X1 \
--to=lee.jones@linaro.org \
--cc=angus.clark@st.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.com \
/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