All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "King, Steven R" <steven.r.king@intel.com>
Cc: linux-kernel@vger.kernel.org, infiniband-general@lists.sourceforge.net
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in the linux kernel
Date: Thu, 5 Feb 2004 13:51:38 -0800	[thread overview]
Message-ID: <20040205215138.GD15718@kroah.com> (raw)
In-Reply-To: <33561BB7A415E04FBDC339D5E149C6E26C38FE@orsmsx405.jf.intel.com>

On Thu, Feb 05, 2004 at 11:38:44AM -0800, King, Steven R wrote:
> We just use the kernel's spin_lock_irqsave(), so I don't know what
> you're talking about.

If you peruse the section, "The Fucked Up Sparc" in
Documentation/DocBook/kernel-locking you will see the problem.

thanks,

greg k-h

  reply	other threads:[~2004-02-05 21:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 19:38 [Infiniband-general] Getting an Infiniband access layer in the linux kernel King, Steven R
2004-02-05 21:51 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 20:16 Woodruff, Robert J
2004-02-05 21:54 ` Greg KH
2004-02-06 23:20   ` Jamie Lokier
2004-02-05 19:44 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 20:16 ` Greg KH
2004-02-05 19:31 [Infiniband-general] Getting an Infiniband access layer in the linux kernel Raj, Ashok
     [not found] <33561BB7A415E04FBDC339D5E149C6E26C38FA@orsmsx405.jf.intel.com>
2004-02-05 18:55 ` Greg KH
2004-02-05 18:34 Raj, Ashok
2004-02-05 18:31 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 18:40 ` Greg KH
2004-02-05 18:53 ` Randy.Dunlap
2004-02-07  2:54 ` Jamie Lokier
     [not found] <C1B7430B33A4B14F80D29B5126C5E94703262582@orsmsx401.jf.intel.com>
2004-02-05 18:09 ` [Infiniband-general] Getting an Infiniband access layer in the linux kernel Greg KH
2004-02-04  4:53 Woodruff, Robert J
2004-02-04  2:01 Woodruff, Robert J
2004-02-04  4:08 ` Troy Benjegerdes
2004-02-04  0:17 Woodruff, Robert J
2004-02-04  1:03 ` Greg KH
2004-02-03 16:45 Woodruff, Robert J
2004-02-04 11:26 ` Masanori ITOH
2004-02-02 23:58 Woodruff, Robert J
2004-02-03  0:56 ` Greg KH
2004-02-03  1:38 ` Masanori ITOH
2004-02-03 22:37 ` Troy Benjegerdes

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=20040205215138.GD15718@kroah.com \
    --to=greg@kroah.com \
    --cc=infiniband-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steven.r.king@intel.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 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.