From: Andrew Morton <akpm@osdl.org>
To: Nicolas Boichat <nicolas@boichat.ch>
Cc: adaplas@pol.net, greg@kroah.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Fw: Rivafb I2C problem, new patch
Date: Tue, 13 Jul 2004 15:02:35 -0700 [thread overview]
Message-ID: <20040713150235.056f6a5c.akpm@osdl.org> (raw)
In-Reply-To: <1089755194.6181.47.camel@tom>
Nicolas Boichat <nicolas@boichat.ch> wrote:
>
> Good idea... it didn't compile. Fixed patch attached.
Please send a complete new patch, with a changelog.
Thanks.
-------------------------------------------------------
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-07-13 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:39 Fw: Rivafb I2C problem, new patch Andrew Morton
2004-07-12 23:43 ` Greg KH
2004-07-13 1:58 ` Antonino A. Daplas
2004-07-13 9:53 ` Nicolas Boichat
2004-07-13 20:52 ` Antonino A. Daplas
2004-07-13 21:46 ` Nicolas Boichat
2004-07-13 22:02 ` Andrew Morton [this message]
2004-07-13 23:45 ` Nicolas Boichat
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=20040713150235.056f6a5c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@pol.net \
--cc=greg@kroah.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=nicolas@boichat.ch \
/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).