public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][MIPS] wire up tee system call
Date: Mon, 26 Jun 2006 14:38:37 +0100	[thread overview]
Message-ID: <20060626133837.GA4583@linux-mips.org> (raw)
In-Reply-To: <200606261251.k5QCpxpd080229@mbox30.po.2iij.net>

On Mon, Jun 26, 2006 at 09:51:59PM +0900, Yoichi Yuasa wrote:

> It is not in Linus's git yet, but it has been in your git last April.
> What is the reason that you did not send it to upstream?

Glitch.  Waiting for him to pull now this and loads of other stuff.

  Ralf

      reply	other threads:[~2006-06-27 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23  8:07 [PATCH][MIPS] wire up tee system call Yoichi Yuasa
2006-06-23  8:11 ` Andrew Morton
2006-06-26  5:27   ` Yoichi Yuasa
2006-06-23 10:02 ` Ralf Baechle
2006-06-26 12:51   ` Yoichi Yuasa
2006-06-26 13:38     ` Ralf Baechle [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=20060626133837.GA4583@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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