From: Richard Smith <rsmith@bitworks.com>
To: Thomas.Jahns@epost.de
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: New fbdev patch.
Date: Tue, 29 Jun 2004 17:27:25 -0500 [thread overview]
Message-ID: <40E1ECCD.7080501@bitworks.com> (raw)
In-Reply-To: <20040629214850.GC2871@mercury.jahnsnet.de>
Thomas Jahns wrote:
You only replied to me so I'm bouncing this to the list as well. James
you want to retry your patch?
> Hi,
>
> On 06/25/04 16:11:24, Richard Smith wrote:
>
>> Has anyone else tried this? A lot of it fails to apply for me. I
>> pulled a clean 2.6.7 from kernel.org.
>>
>> A large portion of the diffs succeed but with an offset.
>
>
> same here, and for some rejects I'm not even able to figure out where
> they are supposed to fit because no meaningful identifier in the
> context appears in the affected source files.
>
> The individual parts of the patch reveal, that it's not against
> straight 2.6.7 but rather against Linus' current tree at that time.
>
> Thomas Jahns
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-06-29 22:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 18:04 New fbdev patch jsimmons
2004-06-25 14:11 ` Richard Smith
[not found] ` <20040629214850.GC2871@mercury.jahnsnet.de>
2004-06-29 22:27 ` Richard Smith [this message]
2004-06-30 16:57 ` jsimmons
2004-07-02 11:01 ` Thomas Jahns
2004-07-05 10:17 ` Thomas Jahns
-- strict thread matches above, loose matches on Subject: below --
2004-01-09 17:17 [Linux-fbdev-devel] New FBDev patch Kronos
2004-01-09 20:06 ` James Simmons
[not found] <1bRBM-5lD-13@gated-at.bofh.it>
[not found] ` <1bSRe-19C-21@gated-at.bofh.it>
2004-01-09 11:27 ` Andreas Theofilu
2004-01-09 14:10 ` Benjamin Herrenschmidt
2004-01-08 22:03 James Simmons
2004-01-08 22:03 ` James Simmons
2004-01-08 22:56 ` Moritz Muehlenhoff
2004-01-08 23:05 ` Paul Mundt
2004-01-08 23:12 ` Tomas Szepe
2004-01-08 23:12 ` Tomas Szepe
2004-01-09 0:35 ` James Simmons
2004-01-09 0:35 ` James Simmons
2004-01-08 23:26 ` Russell King
2004-01-08 23:26 ` Russell King
2004-01-09 19:54 ` James Simmons
2004-01-09 19:54 ` James Simmons
2004-01-11 12:09 ` Russell King
2004-01-11 12:09 ` Russell King
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=40E1ECCD.7080501@bitworks.com \
--to=rsmith@bitworks.com \
--cc=Thomas.Jahns@epost.de \
--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.