From: Bartlomiej Sieka <tur@semihalf.com>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH][MTD] Fix incorrect interface code for x16/x32 chips
Date: Thu, 10 Jan 2008 10:20:50 +0100 [thread overview]
Message-ID: <4785E372.9010409@semihalf.com> (raw)
In-Reply-To: <4755E020.4070702@semihalf.com>
Bartlomiej Sieka wrote:
> Bartlomiej Sieka wrote:
>> According to "Common Flash Memory Interface Publication 100" dated
>> December 1, 2001, the interface code for x16/x32 chips is 0x0005,
>> and not 0x0004 used so far.
>>
>> Signed-off-by: Bartlomiej Sieka <tur@semihalf.com>
>
> I'd appreciate some feedback on the status of this patch.
Hmm, it's been over a month now since the patch has been posted, and
there haven't been any comments, acceptance/rejection notices, etc. Is
this a wrong list to post this patch? Did I miss some formal requirement
or something? Are people just too busy?
Regards,
Bartlomiej
next prev parent reply other threads:[~2008-01-10 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 17:55 [PATCH][MTD] Fix incorrect interface code for x16/x32 chips Bartlomiej Sieka
2007-12-04 23:17 ` Bartlomiej Sieka
2008-01-10 9:20 ` Bartlomiej Sieka [this message]
2008-01-10 11:03 ` Jörn Engel
2008-01-10 22:11 ` David Woodhouse
2008-01-11 15:27 ` Bartlomiej Sieka
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=4785E372.9010409@semihalf.com \
--to=tur@semihalf.com \
--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