Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Koeller <thomas@koeller.dyndns.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Patches
Date: Wed, 13 Sep 2006 13:27:46 +0100	[thread overview]
Message-ID: <20060913122746.GA10177@linux-mips.org> (raw)
In-Reply-To: <200609122247.19091.thomas@koeller.dyndns.org>

On Tue, Sep 12, 2006 at 10:47:19PM +0200, Thomas Koeller wrote:

> what about these patches:
> http://www.linux-mips.org/archives/linux-mips/2006-08/msg00271.html
> http://www.linux-mips.org/archives/linux-mips/2006-08/msg00270.html
> 
> Are you going to apply them?

They've been applied to the queue branch weeks ago.  Due to the still
unmerged RM92xx seriver driver I didn't consider it 2.6.18 material.

  Ralf

  reply	other threads:[~2006-09-13 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 20:47 Patches Thomas Koeller
2006-09-13 12:27 ` Ralf Baechle [this message]
2006-09-13 13:02   ` Patches Franck Bui-Huu
  -- strict thread matches above, loose matches on Subject: below --
2000-07-08  0:17 Patches Ralf Baechle

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=20060913122746.GA10177@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=thomas@koeller.dyndns.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