From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
Sylvain Meyer <sylvain.meyer@worldonline.fr>,
Pavel Kysilka <goldenfish@bsys.cz>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/2] intelfb/fbdev: Save info->flags in a local variable
Date: Tue, 16 Aug 2005 05:51:11 +0800 [thread overview]
Message-ID: <43010E4F.6090502@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508150957230.3553@g5.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 15 Aug 2005, Antonino A. Daplas wrote:
>> @@ -697,7 +697,7 @@ fb_set_var(struct fb_info *info, struct
>> !list_empty(&info->modelist))
>> err = fb_add_videomode(&mode, &info->modelist);
>>
>> - if (!err && info->flags & FBINFO_MISC_USEREVENT) {
>> + if (!err && flags & FBINFO_MISC_USEREVENT) {
>> struct fb_event event;
>> int evnt = (var->activate & FB_ACTIVATE_ALL) ?
>> FB_EVENT_MODE_CHANGE_ALL :
>
> This doesn't match my tree - I assume we're talking about the -mm tree
> here.
>
> I can/will fix up the thing by hand, but somebody should check it.
>
> Linus
>
Sorry about that, I forgot. I checked your git tree, and it looks good.
Thanks.
Tony
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
prev parent reply other threads:[~2005-08-15 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 13:29 [PATCH 2/2] intelfb/fbdev: Save info->flags in a local variable Antonino A. Daplas
2005-08-15 16:28 ` James Simmons
2005-08-15 16:31 ` James Simmons
2005-08-15 16:58 ` Linus Torvalds
2005-08-15 21:51 ` Antonino A. Daplas [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=43010E4F.6090502@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=goldenfish@bsys.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sylvain.meyer@worldonline.fr \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.