From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-fbdev@vger.kernel.org, xen-devel@lists.xensource.com,
jirislaby@gmail.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 3/3] VIDEO: xen-fb, switch to for_each_console
Date: Thu, 04 Nov 2010 11:20:42 -0400 [thread overview]
Message-ID: <4CD2CF4A.9080503@goop.org> (raw)
In-Reply-To: <1288798114-23206-3-git-send-email-jslaby@suse.cz>
On 11/03/2010 11:28 AM, Jiri Slaby wrote:
> Use newly added for_each_console for iterating consoles.
>
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Cc: Jeremy Fitzhardinge <jeremy@xensource.com>
Sure, if that's what all the kids are doing these days.
Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
J
> Cc: Chris Wright <chrisw@sous-sol.org>
> Cc: virtualization@lists.osdl.org
> Cc: xen-devel@lists.xensource.com
> Cc: linux-fbdev@vger.kernel.org
> ---
> drivers/video/xen-fbfront.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/video/xen-fbfront.c b/drivers/video/xen-fbfront.c
> index 428d273..4abb0b9 100644
> --- a/drivers/video/xen-fbfront.c
> +++ b/drivers/video/xen-fbfront.c
> @@ -492,7 +492,7 @@ xenfb_make_preferred_console(void)
> return;
>
> acquire_console_sem();
> - for (c = console_drivers; c; c = c->next) {
> + for_each_console(c) {
> if (!strcmp(c->name, "tty") && c->index == 0)
> break;
> }
prev parent reply other threads:[~2010-11-04 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1288798114-23206-1-git-send-email-jslaby@suse.cz>
2010-11-03 15:28 ` [PATCH 3/3] VIDEO: xen-fb, switch to for_each_console Jiri Slaby
2010-11-04 15:20 ` Jeremy Fitzhardinge [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=4CD2CF4A.9080503@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=konrad.wilk@oracle.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).