From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Peter Samuelson <peter@p12n.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] con2fbmap limit check
Date: Wed, 31 Oct 2007 20:48:37 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0710312048270.12491@anakin> (raw)
In-Reply-To: <20071031145819.GB27631@p12n.org>
On Wed, 31 Oct 2007, Peter Samuelson wrote:
> Trivial patch to avoid an oops I hit when trying to figure out how to
> use con2fbmap.
No patch included?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-31 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 14:58 [patch] con2fbmap limit check Peter Samuelson
2007-10-31 19:48 ` Geert Uytterhoeven [this message]
2007-10-31 20:50 ` Peter Samuelson
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=Pine.LNX.4.64.0710312048270.12491@anakin \
--to=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=peter@p12n.org \
/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).