From: Krzysztof Halasa <khc@pm.waw.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
sylvain.meyer@worldonline.fr, linux-kernel@vger.kernel.org,
"Antonino A. Daplas" <adaplas@pol.net>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] Intel FB pixel clock calculation fix
Date: Fri, 26 Oct 2007 21:58:05 +0200 [thread overview]
Message-ID: <m33avxlkc2.fsf@maximus.localdomain> (raw)
In-Reply-To: <20071026175143.GB1573@elf.ucw.cz> (Pavel Machek's message of "Fri, 26 Oct 2007 19:51:43 +0200")
Pavel Machek <pavel@ucw.cz> writes:
> On Tue 2007-09-11 14:18:57, Krzysztof Halasa wrote:
>> I think 2.6.22 would be overkill, .23 - not sure.
>
> I don't think this is -stable kind of bug.
Given the timeframe, I can only agree once again :-)
--
Krzysztof Halasa
prev parent reply other threads:[~2007-10-26 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3ir6il3wl.fsf@maximus.localdomain>
2007-09-11 5:52 ` [PATCH] Intel FB pixel clock calculation fix Andrew Morton
2007-09-11 12:18 ` Krzysztof Halasa
2007-09-12 4:17 ` suresh gani
2007-10-26 17:51 ` Pavel Machek
2007-10-26 19:58 ` Krzysztof Halasa [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=m33avxlkc2.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=adaplas@pol.net \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sylvain.meyer@worldonline.fr \
/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).