From: "David S. Miller" <davem@redhat.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-arch@vger.kernel.org
Subject: Re: Future of linux-arch
Date: Sun, 28 Mar 2004 12:29:20 -0800 [thread overview]
Message-ID: <20040328122920.404e5b37.davem@redhat.com> (raw)
In-Reply-To: <20040328120133.D2825@flint.arm.linux.org.uk>
On Sun, 28 Mar 2004 12:01:33 +0100
Russell King <rmk@arm.linux.org.uk> wrote:
> It seems that me posting these two patches just to linux-arch has caused
> some upset in the kernel community. In particular, Christoph Hellwig
> is talking about publicising the address for this list.
If he can't respect people's privacy, that shouldn't become our problem.
If a group of people interested in 'foo' wish to discuss 'foo' on a mailing
list amongst themselves, I don't see what can be wrong with that.
Maybe I should feel compelled to CC: lkml every time I come up with an
idea I wish to discuss with Linux or Andrew or one of the networking
co-maintainers? See how rediculious such thinking is?
Now, on the other hand, it may have in fact been more appropriate to discuss
this particular change on lkml, flesh out the API issues publicly, _then_
move what you end up with to linux-arch so that arch people can code up
implementations for their platforms for you.
See, because this patch goes beyond arch issues, driver folks have to use
these interfaces, so logically it appears that folks outside of the arch
community should contribute to the design and review of said interfaces.
Right?
next prev parent reply other threads:[~2004-03-28 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 11:01 Future of linux-arch Russell King
2004-03-28 20:29 ` David S. Miller [this message]
2004-03-28 20:48 ` Russell King
2004-03-28 20:55 ` David S. Miller
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=20040328122920.404e5b37.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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