From: Greg KH <greg@kroah.com>
To: "Woodruff, Robert J" <woody@co.intel.com>
Cc: "Hefty, Sean" <sean.hefty@intel.com>,
"Tillier, Fabian" <ftillier@infiniconsys.com>,
Chris Friesen <cfriesen@nortelnetworks.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org, hozer@hozed.org, "Woodruff,
Robert J" <woody@jf.intel.com>,
"Magro, Bill" <bill.magro@intel.com>,
infiniband-general@lists.sourceforge.net
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in theLinux kernel
Date: Tue, 24 Feb 2004 10:03:04 -0800 [thread overview]
Message-ID: <20040224180304.GA31826@kroah.com> (raw)
In-Reply-To: <F595A0622682C44DBBE0BBA91E56A5ED1C36C4@orsmsx410.jf.intel.com>
On Tue, Feb 24, 2004 at 09:55:25AM -0800, Woodruff, Robert J wrote:
>
> Would you like me to submit the patch directly to linux-kernel email
> list ?
Yes, please do. If you want, feel free to cc: me also.
But as you have not cleaned up the stuff that everyone has already told
you to clean up, it might be pretty pointless to do so without fixing
that code first. In fact, why even post a patch without making those,
necessary changes?
thanks,
greg k-h
next prev parent reply other threads:[~2004-02-24 18:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 17:55 [Infiniband-general] Getting an Infiniband access layer in theLinux kernel Woodruff, Robert J
2004-02-24 18:03 ` Greg KH [this message]
[not found] <mailman.1076018705.12618.linux-kernel2news@redhat.com>
2004-02-09 1:51 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2004-02-08 23:43 Arnd Bergmann
2004-02-08 21:36 Woodruff, Robert J
2004-02-06 16:42 Hefty, Sean
2004-02-06 17:05 ` Richard B. Johnson
2004-02-06 17:23 ` Roland Dreier
2004-02-06 18:00 ` Richard B. Johnson
2004-02-06 18:12 ` Måns Rullgård
2004-02-06 18:13 ` Chris Friesen
2004-02-06 18:22 ` Valdis.Kletnieks
2004-02-06 18:50 ` Richard B. Johnson
2004-02-06 19:02 ` Matti Aarnio
2004-02-06 19:11 ` Petr Vandrovec
2004-02-07 3:05 ` Jamie Lokier
2004-02-06 18:54 ` Måns Rullgård
2004-02-06 19:01 ` somenath
2004-02-06 17:27 ` Troy Benjegerdes
2004-02-06 18:51 ` Greg KH
2004-02-08 8:31 ` Fab Tillier
2004-02-08 16:29 ` Greg KH
2004-02-08 16:51 ` Fab Tillier
2004-02-09 2:55 ` Troy Benjegerdes
2004-02-09 2:57 ` Greg KH
2004-02-06 4:07 Perez-Gonzalez, Inaky
2004-02-05 23:09 Woodruff, Robert J
2004-02-05 22:55 Woodruff, Robert J
2004-02-05 22:54 ` Randy.Dunlap
2004-02-05 22:26 Hefty, Sean
2004-02-05 22:40 ` Christoph Hellwig
2004-02-05 22:39 ` Randy.Dunlap
2004-02-05 23:19 ` Greg KH
2004-02-06 1:10 ` Troy Benjegerdes
2004-02-05 22:17 Tillier, Fabian
2004-02-05 22:56 ` Brian Gerst
2004-02-05 22:58 ` Bernd Petrovitsch
2004-02-05 22:02 Tillier, Fabian
2004-02-06 1:57 ` Troy Benjegerdes
2004-02-05 20:32 Tillier, Fabian
2004-02-05 21:27 ` Greg KH
2004-02-05 21:56 ` Chris Friesen
2004-02-06 20:22 ` Bill Davidsen
2004-02-05 19:26 Tillier, Fabian
2004-02-05 20:27 ` Greg KH
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=20040224180304.GA31826@kroah.com \
--to=greg@kroah.com \
--cc=bill.magro@intel.com \
--cc=cfriesen@nortelnetworks.com \
--cc=ftillier@infiniconsys.com \
--cc=hozer@hozed.org \
--cc=infiniband-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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