From: Marc Singer <elf@buici.com>
To: linux-mtd@lists.infradead.org
Subject: Re: cmdlineparts and chip initialization order
Date: Fri, 12 Nov 2004 02:27:46 -0800 [thread overview]
Message-ID: <20041112102746.GA27967@buici.com> (raw)
In-Reply-To: <1100213473.5074.81.camel@thomas>
I now understand why the partitions weren't being parsed. I didn't
realize that the driver itself was responsible for calling the code
that parses partitions.
Cheers.
next prev parent reply other threads:[~2004-11-12 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 22:01 cmdlineparts and chip initialization order Marc Singer
2004-11-11 22:51 ` Thomas Gleixner
2004-11-12 10:18 ` Marc Singer
2004-11-12 10:27 ` Marc Singer [this message]
2004-11-11 23:18 ` Aras Vaichas
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=20041112102746.GA27967@buici.com \
--to=elf@buici.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