From: Adam Jackson <ajax@redhat.com>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH] video: Use less worrisome language in fbdev handoff
Date: Wed, 15 May 2013 21:04:11 +0000 [thread overview]
Message-ID: <1368651851-14326-1-git-send-email-ajax@redhat.com> (raw)
For some reason people see "conflicting" and think it's a problem, even
though it's totally normal. Just call it a handoff.
Signed-off-by: Adam Jackson <ajax@redhat.com>
---
drivers/video/fbmem.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/video/fbmem.c b/drivers/video/fbmem.c
index 098bfc6..2ec56a2 100644
--- a/drivers/video/fbmem.c
+++ b/drivers/video/fbmem.c
@@ -1576,10 +1576,9 @@ static void do_remove_conflicting_framebuffers(struct apertures_struct *a,
if (fb_do_apertures_overlap(gen_aper, a) ||
(primary && gen_aper && gen_aper->count &&
gen_aper->ranges[0].base = VGA_FB_PHYS)) {
-
- printk(KERN_INFO "fb: conflicting fb hw usage "
- "%s vs %s - removing generic driver\n",
- name, registered_fb[i]->fix.id);
+ printk(KERN_INFO "fb: Handoff from generic %s "
+ "driver to %s\n", registered_fb[i]->fix.id,
+ name);
do_unregister_framebuffer(registered_fb[i]);
}
}
--
1.8.2.1
reply other threads:[~2013-05-15 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1368651851-14326-1-git-send-email-ajax@redhat.com \
--to=ajax@redhat.com \
--cc=linux-fbdev@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).