From: Ondrej Zary <linux@rainbow-software.org>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: [PATCH] i740fb: fix compile error when CONFIG_MTRR is not selected
Date: Mon, 20 Feb 2012 20:49:47 +0000 [thread overview]
Message-ID: <201202202149.52869.linux@rainbow-software.org> (raw)
In-Reply-To: <1329687211-6545-1-git-send-email-FlorianSchandinat@gmx.de>
On Sunday 19 February 2012 22:33:31 Florian Tobias Schandinat wrote:
> Signed-off-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
> ---
> drivers/video/i740fb.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/video/i740fb.c b/drivers/video/i740fb.c
> index 8be0302..fe574d8 100644
> --- a/drivers/video/i740fb.c
> +++ b/drivers/video/i740fb.c
> @@ -1179,9 +1179,9 @@ static void __devexit i740fb_remove(struct pci_dev
> *dev) struct fb_info *info = pci_get_drvdata(dev);
>
> if (info) {
> -#ifdef CONFIG_MTRR
> struct i740fb_par *par = info->par;
>
> +#ifdef CONFIG_MTRR
> if (par->mtrr_reg >= 0) {
> mtrr_del(par->mtrr_reg, 0, 0);
> par->mtrr_reg = -1;
Thanks for fixing my stupid bug. I thought that I tested it without
CONFIG_MTRR. But obviously didn't.
--
Ondrej Zary
next prev parent reply other threads:[~2012-02-20 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 6:32 linux-next: build failure after merge of the final tree Stephen Rothwell
2012-02-16 5:29 ` linux-next: build failure after merge of the final tree (fbdev tree related) Stephen Rothwell
2012-02-19 21:33 ` [PATCH] i740fb: fix compile error when CONFIG_MTRR is not selected Florian Tobias Schandinat
2012-02-20 20:49 ` Ondrej Zary [this message]
2013-10-28 14:23 ` linux-next: build failure after merge of the final tree (fbdev tree related) Stephen Rothwell
2013-10-28 14:39 ` Michal Simek
2013-10-29 8:50 ` Tomi Valkeinen
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=201202202149.52869.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).