From: "David S. Miller" <davem@redhat.com>
To: roland@topspin.com
Cc: hch@infradead.org, jmorris@intercode.com.au, TSPAT@de.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: crypto API and IBM z990 hardware support
Date: Mon, 07 Jul 2003 20:35:16 -0700 (PDT) [thread overview]
Message-ID: <20030707.203516.23026768.davem@redhat.com> (raw)
In-Reply-To: <52adbp1yfu.fsf@topspin.com>
From: Roland Dreier <roland@topspin.com>
Date: 07 Jul 2003 20:37:09 -0700
Still, I think there is a lot to be said for keeping arch code in
arch/xxx and include/asm-xxx. It means that someone working on a
new port (I don't necessarily mean a totally new arch, but also
adding support for some new CPU model or platform) has a
well-defined set of directories to look at.
I again disagree. We're talking about things here where
the default you get is _working_.
Only if you want to enhance or _optimize_ your port do you
need to modify any of this crap.
In this way it's fundamentally different from things that
one normally finds under arch/foo and include/asm-foo
It's also nice that the xxx-arch maintainers can say "we are the rulers
of arch/xxx and include/asm-xxx" and know that any changes outside of
those directories have to go through lkml.
This isn't nice, it's rather bad for this case.
I think it'd be great that the "crypto maintainer" can be the one
by which "crypto changes" need to go through. So again, I totally
disagree with your assesment.
Still, I don't think I would like it if we had
alpha/ arm/ arm26/ cris/ h8300/ i386/ ia64/ m68k/ m68knommu/
mips/ mips64/ parisc ppc/ ppc64/ s390/ sh/ sparc/ sparc64/ um/
v850/ x86_64/ generic/
directories scattered all over the source tree.
I see no problem with this at all. In fact, I wish we had a much
higher directory to file ratio in the kernel tree.
And hey, if I went "find crypto -type d -name sparc" I'd know if there
are sparc optimizations for the crypto library. How might you do this
with the current "everything and it's mother under arch/" scheme?
Answer: you can't.
next prev parent reply other threads:[~2003-07-08 3:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 7:07 crypto API and IBM z990 hardware support Thomas Spatzier
2003-07-02 9:35 ` James Morris
2003-07-07 7:09 ` Christoph Hellwig
2003-07-08 2:53 ` David S. Miller
2003-07-08 3:37 ` Roland Dreier
2003-07-08 3:35 ` David S. Miller [this message]
2003-07-10 1:08 ` Werner Almesberger
2003-07-10 1:08 ` David S. Miller
2003-07-10 2:06 ` Werner Almesberger
2003-07-10 2:06 ` David S. Miller
2003-07-10 2:37 ` Werner Almesberger
2003-07-11 0:02 ` David S. Miller
[not found] ` <mailman.1057799700.15422.linux-kernel2news@redhat.com>
2003-07-10 5:55 ` Pete Zaitcev
2003-07-02 12:35 Thomas Spatzier
2003-07-02 16:57 ` James Morris
2003-07-07 7:11 ` Christoph Hellwig
2003-07-07 10:27 ` James Morris
2003-07-02 20:23 Ulrich Weigand
[not found] <4P45.5YN.11@gated-at.bofh.it>
[not found] ` <4T81.24d.41@gated-at.bofh.it>
2003-07-02 22:06 ` Arnd Bergmann
2003-07-06 14:08 ` James Morris
2003-07-06 17:46 ` Arnd Bergmann
2003-07-07 7:14 ` 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=20030707.203516.23026768.davem@redhat.com \
--to=davem@redhat.com \
--cc=TSPAT@de.ibm.com \
--cc=hch@infradead.org \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.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;
as well as URLs for NNTP newsgroup(s).