All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jean Delvare" <khali@linux-fr.org>
To: benh@kernel.crashing.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] radeonfb: prevent spurious recompilations
Date: Wed, 12 Oct 2005 12:36:58 +0200 (CEST)	[thread overview]
Message-ID: <7Zcgfrp8.1129113418.6878470.khali@localhost> (raw)
In-Reply-To: <1129112951.5213.0.camel@gaston>


Hi Ben,

On 2005-10-12, Benjamin Herrenschmidt wrote:
> Nah, just submit that patch for now, I'll do a better fix later

Submit to whom? I thought you were the right person (and the
linux-fbdev-devel list the right place) to submit it to.

Thanks,
--
Jean Delvare


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

      reply	other threads:[~2005-10-12 10:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 19:55 [PATCH] radeonfb: prevent spurious recompilations Jean Delvare
2005-10-11 20:59 ` Benjamin Herrenschmidt
2005-10-12  8:31   ` Jean Delvare
2005-10-12 10:29     ` Benjamin Herrenschmidt
2005-10-12 10:36       ` Jean Delvare [this message]

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=7Zcgfrp8.1129113418.6878470.khali@localhost \
    --to=khali@linux-fr.org \
    --cc=benh@kernel.crashing.org \
    --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.