From: Brian Norris <computersforpeace@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: maps: remove check for CONFIG_MTD_SUPERH_RESERVE
Date: Wed, 28 May 2014 15:33:49 -0700 [thread overview]
Message-ID: <20140528223349.GF3599@ld-irv-0074> (raw)
In-Reply-To: <1400855394.31526.37.camel@x220>
On Fri, May 23, 2014 at 04:29:54PM +0200, Paul Bolle wrote:
> Since (a few releases before) v2.6.0 there have been checks for
> CONFIG_MTD_SUPERH_RESERVE. One check is still present. But a Kconfig
> symbol MTD_SUPERH_RESERVE has never been added. So a few lines of dead
> code can be removed.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Untested.
Compile-tested and pushed to l2-mtd.git. Thanks!
Brian
prev parent reply other threads:[~2014-05-28 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 14:29 [PATCH] mtd: maps: remove check for CONFIG_MTD_SUPERH_RESERVE Paul Bolle
2014-05-28 22:33 ` Brian Norris [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=20140528223349.GF3599@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pebolle@tiscali.nl \
/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