public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Proposal] DEBUG_SLAB should select DEBUG_SPINLOCK
Date: 28 May 2004 12:54:35 -0700	[thread overview]
Message-ID: <52zn7s5nus.fsf@topspin.com> (raw)
In-Reply-To: <20040528124228.105ebcbb.rddunlap@osdl.org>

    Randy> Andrew asked me to delay it until 2.6.6, which I did.  Sent
    Randy> that, but not merged.

    Randy> I will be rediffing it and resending it again for 2.6.7 and
    Randy> probably some intermediate kernels if that's what it takes.

Thanks for the info.  I guess I'll wait for your patch to be merged
and then send my (trivial) patch.

 - Roland

  reply	other threads:[~2004-05-28 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 19:45 [Proposal] DEBUG_SLAB should select DEBUG_SPINLOCK Roland Dreier
2004-05-28 19:42 ` Randy.Dunlap
2004-05-28 19:54   ` Roland Dreier [this message]
2004-05-28 20:00     ` Randy.Dunlap
2004-05-28 20:35       ` Roland Dreier

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=52zn7s5nus.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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