From: Raphael Assenat <raph@8d.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] cmx270-nand: Make CMDLINE_PARTS usable
Date: Fri, 22 Sep 2006 10:15:57 -0400 [thread overview]
Message-ID: <4513F01D.80608@8d.com> (raw)
In-Reply-To: <1158917790.24527.664.camel@pmac.infradead.org>
David Woodhouse wrote:
> On Wed, 2006-09-13 at 08:50 -0400, Raphael Assenat wrote:
>
>>This patch gives a name to the cmx270 nand mtd, making it possible to
>>use command line partitioning.
>
>
> Er, there _is_ no cmx270 nand board driver in my tree.
>
Oh, sorry. My patch applies over the patch Mike Rapoport sent to the list on July 18
([PATCH] [MTD] CM-x270 NAND flash support), which I thought was already accepted. Was
there anything wrong with it? Maybe you just missed it...
I also sent a patch to the list on July 21 which added NAND flash support for the cm-x255
boards ([PATCH] Add support for NAND flash on cm-x255) but received no feedback. I can
resend it if you wish.
(BTW, every time I send to the linux-mtd list my message is held for moderator approval
for reason 'Message has a suspicious header'. Who should I contact for more information?
I'd like to know exactly what header(s) is/are 'suspicious' and fix them if possible).
Best regards,
--
Raphael Assenat
8D Technologies Inc.
next prev parent reply other threads:[~2006-09-22 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 12:50 [PATCH] cmx270-nand: Make CMDLINE_PARTS usable Raphael Assenat
2006-09-22 9:36 ` David Woodhouse
2006-09-22 14:15 ` Raphael Assenat [this message]
2006-09-22 14:44 ` David Woodhouse
2006-09-25 13:07 ` Raphael Assenat
2006-09-25 14:57 ` Raphael Assenat
2006-09-25 14:22 ` [PATCH][RESEND] [MTD] CM-x270 NAND flash support (Was [PATCH] cmx270-nand: Make CMDLINE_PARTS usable) Mike Rapoport
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=4513F01D.80608@8d.com \
--to=raph@8d.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox