From: Nivedita Singhvi <niv@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Date: Sun, 14 Mar 2004 15:14:28 -0800 [thread overview]
Message-ID: <4054E754.70602@us.ibm.com> (raw)
> That is, of course, an excellent approach.
>
> But beware of being *too* disconnected from the lists@vger.kernel.org. We
> don't want to get in the situation where you pop up with a couple of
> person-years' worth of work and other kernel developers have major issues
> with it. Please find a balance - some way of regularly checkpointing.
Andrew,
Thanks. I had wanted to convey the gist of what you say to someone
earlier this week. It would have been nice to point to some document
that captures this, and though I looked around, I haven't found anything
in one place, surprisingly. It's a plea kernel maintainers frequently make
to Linux contributors, but new projects seem to run into the same problems
repeatedly. I figured it would be worth putting together your comments
and some basic related advice given to those wishing to get their
code into the kernel in a document. Hope that's ok.
File follows in a separate mail.
thanks,
Nivedita
next reply other threads:[~2004-03-14 23:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 23:14 Nivedita Singhvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-20 19:15 PATCH - InfiniBand Access Layer (IBAL) Acker, Dave
2004-03-20 17:15 Acker, Dave
2004-03-20 17:55 ` Ulrich Drepper
2004-03-21 22:16 ` Roland Dreier
2004-03-15 22:52 Woodruff, Robert J
2004-03-15 23:17 ` Christoph Hellwig
2004-03-15 23:44 ` Johannes Erdfelt
2004-03-15 23:48 ` Christoph Hellwig
2004-03-15 23:54 ` Johannes Erdfelt
2004-03-16 0:09 ` Christoph Hellwig
2004-03-16 0:18 ` Johannes Erdfelt
2004-03-16 1:41 ` Roland Dreier
2004-03-19 18:47 ` Ulrich Drepper
2004-03-19 19:21 ` Fab Tillier
2004-03-19 20:20 ` Ulrich Drepper
2004-03-19 20:47 ` Roland Dreier
2004-03-14 3:46 Woodruff, Robert J
2004-03-15 2:10 ` Greg KH
2004-03-13 22:07 Woodruff, Robert J
2004-03-14 1:13 ` Andrew Morton
2004-03-14 2:28 ` Greg KH
2004-02-24 23:02 Woodruff, Robert J
2004-02-25 3:32 ` Rik van Riel
2004-02-24 22:18 Woodruff, Robert J
2004-02-24 21:33 Woodruff, Robert J
2004-02-24 19:29 Woodruff, Robert J
2004-02-24 19:44 ` Greg KH
2004-02-24 19:50 ` Christoph Hellwig
2004-02-24 19:57 ` Greg KH
2004-02-24 22:29 ` Rik van Riel
2004-02-25 0:28 ` Matti Aarnio
2004-02-25 3:39 ` Rik van Riel
2004-02-25 16:25 ` Timothy Miller
2004-02-25 17:34 ` Roland Dreier
2004-02-25 18:55 ` Sam Ravnborg
2004-02-25 18:05 ` Linus Torvalds
2004-02-25 19:09 ` Timothy Miller
2004-02-25 19:55 ` Sam Ravnborg
2004-02-25 19:05 ` Linus Torvalds
2004-02-25 13:19 ` Christoph Hellwig
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=4054E754.70602@us.ibm.com \
--to=niv@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 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.