mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Tillier, Fabian" <ftillier@infiniconsys.com>
Cc: "Hefty, Sean" <sean.hefty@intel.com>,
	linux-kernel@vger.kernel.org, Troy Benjegerdes <hozer@hozed.org>,
	"Woodruff, Robert J" <woody@co.intel.com>,
	"Magro, Bill" <bill.magro@intel.com>,
	"Woodruff, Robert J" <woody@jf.intel.com>,
	infiniband-general@lists.sourceforge.net
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in the Linux kernel
Date: Thu, 5 Feb 2004 10:40:33 -0800	[thread overview]
Message-ID: <20040205184033.GB13434@kroah.com> (raw)
In-Reply-To: <08628CA53C6CBA4ABAFB9E808A5214CB01DB96A4@mercury.infiniconsys.com>

On Thu, Feb 05, 2004 at 01:31:45PM -0500, Tillier, Fabian wrote:
> 
> Are you suggesting that if there is any abstraction, the code will never
> be accepted?  Or rather that the abstraction better be correct?  I'm
> hoping for the latter, however please clarify.

The kernel has its own abstractions that seem to be working quite well
for all different types of platforms.  There is no need for you to
create your own, just for a driver subsystem.

If you have found any problems with the current locks please let the
entire kernel community benefit from your changes, and not relegate them
to a infiniband-only section of the kernel.

So yes, if you add your own versions of spinlocks and atomic_t types,
your code will be rejected, among other things :)

thanks,

greg k-h

  reply	other threads:[~2004-02-05 18:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 18:31 Tillier, Fabian
2004-02-05 18:40 ` Greg KH [this message]
2004-02-05 18:53 ` Randy.Dunlap
2004-02-07  2:54 ` Jamie Lokier
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 20:16 [Infiniband-general] Getting an Infiniband access layer in the linux kernel 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:38 [Infiniband-general] Getting an Infiniband access layer in the linux kernel King, Steven R
2004-02-05 21:51 ` Greg KH
2004-02-05 19:31 Raj, Ashok
     [not found] <33561BB7A415E04FBDC339D5E149C6E26C38FA@orsmsx405.jf.intel.com>
2004-02-05 18:55 ` Greg KH
2004-02-05 18:34 Raj, Ashok
     [not found] <C1B7430B33A4B14F80D29B5126C5E94703262582@orsmsx401.jf.intel.com>
2004-02-05 18:09 ` 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=20040205184033.GB13434@kroah.com \
    --to=greg@kroah.com \
    --cc=bill.magro@intel.com \
    --cc=ftillier@infiniconsys.com \
    --cc=hozer@hozed.org \
    --cc=infiniband-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.hefty@intel.com \
    --cc=woody@co.intel.com \
    --cc=woody@jf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®