From: Paul Bolle <pebolle@tiscali.nl>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] video: nuc900fb: remove "config FB_NUC900_DEBUG"
Date: Thu, 21 Mar 2013 20:27:36 +0000 [thread overview]
Message-ID: <1363897656.1390.155.camel@x61.thuisdomein> (raw)
In-Reply-To: <1363897258.1390.153.camel@x61.thuisdomein>
On Thu, 2013-03-21 at 21:20 +0100, Paul Bolle wrote:
> When the NUC900 LCD Controller Driver got added (in v3.4) a Kconfig
> entry for FB_NUC900_DEBUG got added too. It has never been used. It
> appears that its users were dropped during review. Anyhow, this entry
> can be removed.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Please s/v3.4/v2.6.34/.
Paul Bolle
prev parent reply other threads:[~2013-03-21 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 20:20 [PATCH] video: nuc900fb: remove "config FB_NUC900_DEBUG" Paul Bolle
2013-03-21 20:27 ` Paul Bolle [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=1363897656.1390.155.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).