From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Wang YanQing <udknight@gmail.com>
Cc: FlorianSchandinat@gmx.de, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, spock@gentoo.org
Subject: Re: [PATCH] video:uvesafb: Fix oops that uvesafb try to execute NX-protected page
Date: Tue, 10 Apr 2012 15:28:27 +0100 [thread overview]
Message-ID: <20120410152827.3fd489f6@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120410064918.GA7611@udknight>
> Hi Alan, are you decided to not reply this any?
I'm not aware of anythign that needs adding to this. Any logic about
whether PCI BIOS methods can be called belongs in the PCI layer, as does
the necessary logic for marking ROMs executable if asked by a driver.
uvesafb isn't the only user of PCI methods that may be affected and the
PCI layer is the place that should export the method to decide this.
That will also then work sanely cross platform - since in general on non
x86 boxes the method can simply return "no"
Alan
next prev parent reply other threads:[~2012-04-10 14:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 10:01 Wang YanQing
2012-03-27 13:32 ` Alan Cox
2012-03-28 0:52 ` Wang YanQing
2012-04-01 1:05 ` Wang YanQing
2012-04-10 6:49 ` Wang YanQing
2012-04-10 14:28 ` Alan Cox [this message]
2012-03-28 15:36 ` Hein_Tibosch
2012-03-31 21:31 ` Florian Tobias Schandinat
-- strict thread matches above, loose matches on Subject: below --
2012-04-01 0:54 Wang YanQing
2012-04-12 2:22 ` Florian Tobias Schandinat
2012-04-01 0:47 Wang YanQing
2012-04-01 0:55 ` Wang YanQing
2012-03-02 0:48 Wang YanQing
2012-03-05 0:52 ` Wang YanQing
2012-03-05 7:09 ` Florian Tobias Schandinat
2012-03-05 7:25 ` Wang YanQing
2012-03-09 0:39 ` Michal Januszewski
2012-03-21 18:34 ` Florian Tobias Schandinat
2012-02-29 13:38 Wang YanQing
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=20120410152827.3fd489f6@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.org \
--cc=udknight@gmail.com \
/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
Powered by JetHome