stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: David Herrmann <dh.herrmann@gmail.com>,
	linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
	the arch/x86 maintainers <x86@kernel.org>,
	linux-fbdev@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] x86: sysfb: remove sysfb when probing real hw
Date: Thu, 19 Dec 2013 12:09:08 -0700	[thread overview]
Message-ID: <52B34454.1040603@wwwdotorg.org> (raw)
In-Reply-To: <20131219185517.GA303@gmail.com>

On 12/19/2013 11:55 AM, Ingo Molnar wrote:
> 
> * Stephen Warren <swarren@wwwdotorg.org> wrote:
> 
>> On 12/19/2013 03:13 AM, David Herrmann wrote:
>>> With CONFIG_X86_SYSFB=y, probing real hw-drivers may result in
>>> resource-conflicts and drivers will refuse to load. A call to
>>> request_mem_region() will fail, if the region overlaps with the mem-region
>>> used by simplefb. The common desktop DRM drivers (intel, nouveau, radeon)
>>> are not affected as they don't reserve their resources, but some others
>>> do, including (nvidiafb, cirrus, ..).
>>
>> I have validated that this doesn't cause any regressions on the/a
>> non-x86 platform using simplefb, although given the main point of this
>> patch is to fix issues on x86, I'm rather hesitant to give a tested-by
>> tag in case someone looking back interprets it incorrectly:-)
> 
> Tested-on-ARM-by: Stephen Warren <swarren@wwwdotorg.org>

I suppose with CC: stable there's some precedent for a comment after the
tag, so perhaps:

Tested-by: Stephen Warren <swarren@wwwdotorg.org> # on ARM only


  reply	other threads:[~2013-12-19 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1387374611-12493-1-git-send-email-dh.herrmann@gmail.com>
2013-12-19 10:13 ` [PATCH v3] x86: sysfb: remove sysfb when probing real hw David Herrmann
2013-12-19 16:36   ` Ingo Molnar
2013-12-19 17:03     ` David Herrmann
2013-12-19 17:09       ` Ingo Molnar
2013-12-19 17:18         ` David Herrmann
2013-12-19 17:24   ` [PATCH v4] " David Herrmann
2013-12-19 18:33     ` Ingo Molnar
2013-12-20 14:46       ` David Herrmann
2013-12-19 18:54   ` [PATCH v3] " Stephen Warren
2013-12-19 18:55     ` Ingo Molnar
2013-12-19 19:09       ` Stephen Warren [this message]
2013-12-19 19:19         ` Ingo Molnar

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=52B34454.1040603@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=dh.herrmann@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=x86@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).