From: Andrew Morton <akpm@linux-foundation.org>
To: krzysztof.h1@poczta.fm
Cc: Dave Airlie <airlied@linux.ie>,
Stefan Husemann <shusemann@googlemail.com>,
Keith Packard <keithp@keithp.com>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: intelfb-support-i854.patch
Date: Fri, 10 Apr 2009 01:05:28 -0700 [thread overview]
Message-ID: <20090410010528.09e0e153.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090410073651.365197DC943@f47.poczta.interia.pl>
On 10 Apr 2009 09:36:50 +0200 krzysztof.h1@poczta.fm wrote:
> Andrew Morton napisa__(a):
> >
> > Guys, I've been sitting on this patch for ages because there was some
> > issue wrt interactions with drm (iirc).
> >
> > Could you please refresh our memories on what the problem was and help
> > find the resolution here?
> >
>
> I have searched on the google and there were never a comment about the patch. It just went unnoticed.
>
> It seems safe (only ids are added). The only possible regression is that drm is broken on i854 that previously was not recognized at all.
>
hm, I'm sure that someone had issues, but I grepped all my email and
can't find it.
Oh well, I guess I'll just merge it and see what happens.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
next parent reply other threads:[~2009-04-10 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090410073651.365197DC943@f47.poczta.interia.pl>
2009-04-10 8:05 ` Andrew Morton [this message]
2009-04-10 8:42 ` intelfb-support-i854.patch Dave Airlie
2009-04-10 8:48 ` intelfb-support-i854.patch Andrew Morton
2009-04-17 1:56 ` intelfb-support-i854.patch Luc Verhaegen
2009-04-17 3:57 ` intelfb-support-i854.patch Dave Airlie
2009-04-09 20:35 intelfb-support-i854.patch Andrew Morton
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=20090410010528.09e0e153.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=keithp@keithp.com \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=shusemann@googlemail.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).