From: Richard Purdie <rpurdie@rpsys.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC: 2.6 patch] MTD_NAND_SHARPSL and MTD_NAND_NANDSIM should be tristate's
Date: Fri, 13 Jan 2006 14:45:02 +0000 [thread overview]
Message-ID: <1137163503.6644.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20060113114817.GG29663@stusta.de>
On Fri, 2006-01-13 at 12:48 +0100, Adrian Bunk wrote:
> MTD_NAND=m and MTD_NAND_SHARPSL=y or MTD_NAND_NANDSIM=y are illegal
> combinations that mustn't be allowed.
>
> This patch fixes this bug by making MTD_NAND_SHARPSL and
> MTD_NAND_NANDSIM tristate's.
>
> Additionally, it fixes some whitespace damage at these options.
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> ---
>
> This patch was already sent on:
> - 31 Dec 2005
>
I can ack the MTD_NAND_SHARPSL part of the patch.
Richard
next prev parent reply other threads:[~2006-01-13 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 11:48 [RFC: 2.6 patch] MTD_NAND_SHARPSL and MTD_NAND_NANDSIM should be tristate's Adrian Bunk
2006-01-13 14:45 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-22 17:12 Adrian Bunk
2006-01-22 17:27 ` Artem B. Bityutskiy
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=1137163503.6644.36.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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