From: Artem Bityutskiy <dedekind1@gmail.com>
To: Conke Hu <conke@maxwit.com>
Cc: support@simtec.co.uk, linux-mtd@lists.infradead.org,
linux@simtec.co.uk, ben-linux@fluff.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s3c nand: parsing commad-line partitions prior to set->partitions
Date: Sun, 18 Jul 2010 11:44:08 +0300 [thread overview]
Message-ID: <1279442648.16247.42.camel@localhost.localdomain> (raw)
In-Reply-To: <1278996990-4380-1-git-send-email-conke@maxwit.com>
On Tue, 2010-07-13 at 12:56 +0800, Conke Hu wrote:
> Current driver prevents command-line partitions from being parsed when built-in
> partitions are defined in s3c2410_nand_set object, but it is not desirable in some
> cases. This patch tries to parse commad-line partitions prior to the built-in.
>
> Signed-off-by: Conke Hu <conke@maxwit.com>
Pushed to l2-mtd-2.6.git / master, thanks.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-07-18 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 4:56 [PATCH] s3c nand: parsing commad-line partitions prior to set->partitions Conke Hu
2010-07-18 8:44 ` Artem Bityutskiy [this message]
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=1279442648.16247.42.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=ben-linux@fluff.org \
--cc=conke@maxwit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@simtec.co.uk \
--cc=support@simtec.co.uk \
/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