Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: mingo@elte.hu, linux-mips@linux-mips.org,
	Manish Lachwani <mlachwani@mvista.com>
Subject: Re: [PATCH] Make MIPS udelay() preempt safe
Date: Tue, 20 Mar 2007 10:58:57 +0000	[thread overview]
Message-ID: <20070320105856.GB24181@linux-mips.org> (raw)
In-Reply-To: <20070319234945.GA11944@plexity.net>

On Mon, Mar 19, 2007 at 04:49:45PM -0700, Deepak Saxena wrote:

> Fix MIPS udelay to make is preempt safe under DEBUG_PREEMPT

I don't understand why you're withdrawing this patch - it makes perfect
sense as Atsushi has also already found, so I'm going to apply it.

  Ralf

      parent reply	other threads:[~2007-03-20 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 23:49 [PATCH] Make MIPS udelay() preempt safe Deepak Saxena
2007-03-20  0:03 ` Deepak Saxena
2007-03-20  1:43   ` Atsushi Nemoto
2007-03-20 10:58 ` 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=20070320105856.GB24181@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dsaxena@plexity.net \
    --cc=linux-mips@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=mlachwani@mvista.com \
    /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