From: Jon Smirl <jonsmirl@gmail.com>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] Allow core fb to be built as a module
Date: Thu, 24 Feb 2005 18:16:17 -0500 [thread overview]
Message-ID: <9e47339105022415165ee292e0@mail.gmail.com> (raw)
In-Reply-To: <200502250704.56925.adaplas@hotpop.com>
Can I assume then that it is acceptable and all we are waiting on is 2.6.11?
On Fri, 25 Feb 2005 07:04:49 +0800, Antonino A. Daplas
<adaplas@hotpop.com> wrote:
> On Friday 25 February 2005 04:39, Jon Smirl wrote:
> > I'm starting to get too many patches hanging around. Is there any
> > reason this one can't be pushed up stream? My next target would be the
> > sysfs patch.
>
> Wait until 2.6.11 comes out. Linus will not accept, and Andrew will not
> push patches unless they're bug fixes.
>
> Tony
>
>
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-24 23:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 20:39 [PATCH] Allow core fb to be built as a module Jon Smirl
2005-02-24 23:04 ` Antonino A. Daplas
2005-02-24 23:16 ` Jon Smirl [this message]
2005-02-24 23:20 ` Antonino A. Daplas
2005-02-25 17:57 ` James Simmons
2005-02-25 19:34 ` Jon Smirl
2005-03-01 21:05 ` James Simmons
2005-02-28 20:12 ` James Simmons
2005-03-01 12:31 ` Antonino A. Daplas
2005-03-02 17:28 ` Jon Smirl
2005-03-02 17:32 ` James Simmons
2005-03-02 17:54 ` Jon Smirl
2005-03-02 23:23 ` Jon Smirl
2005-03-02 17:51 ` Paul Mundt
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=9e47339105022415165ee292e0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.