From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Dan Williams" <dan.j.williams@intel.com>
Cc: "Adrian Bunk" <bunk@kernel.org>,
"Sebastian Siewior" <linux-crypto@ml.breakpoint.cc>,
hskinnemoen@atmel.com, herbert@gondor.apana.org.au,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, shannon.nelson@intel.com
Subject: Re: [2.6 patch] add include/asm-avr32/xor.h
Date: Mon, 14 Apr 2008 18:30:47 -0400 [thread overview]
Message-ID: <8bd0f97a0804141530i7c6ee03codeb0a546d333cb2f@mail.gmail.com> (raw)
In-Reply-To: <e9c3a7c20804141527k475ee297wdf1053179abdaaf8@mail.gmail.com>
On Mon, Apr 14, 2008 at 6:27 PM, Dan Williams <dan.j.williams@intel.com> wrote:
> On Mon, Apr 14, 2008 at 3:11 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> > On Mon, Apr 14, 2008 at 6:01 PM, Adrian Bunk <bunk@kernel.org> wrote:
> > > On Mon, Apr 14, 2008 at 11:46:40PM +0200, Sebastian Siewior wrote:
> > > > so most
> > > > xor.h files are identical copies and this is probably as bad as a
> > > > trailing white space :)
> > >
> > > I'm not sure whether it's worth spending my time discussing whether
> > > adding a config variable to 6 architectures is really better than
> > > adding trivial headers to 3 architectures...
> >
> > long term robustness for new ports/codedrops indicates that having a
> > common header in linux/ and making arches opt-in via Kconfig/whatever
> > makes life a lot easier for everyone
> >
> > everything builds by default with the generic C versions and arches
> > dont have to go through and figure out all the fun little stub files
> > they need to straight copy from other architectures ... they only have
> > to care if they want to implement an optimized version
>
> "arches" did not have to go through and figure out the fun little stub
> file for xor.h. Adrian already made your "life easier".
actually he didnt. he posted a fix for avr32. i dont care about
avr32, i'm a blackfin guy. he also wouldnt have had to do anything at
all if everything was handled with indirection in linux/xor.h.
your point also is irrelevant in the case of new architectures. poor
microblaze for example.
-mike
next prev parent reply other threads:[~2008-04-14 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 14:16 [2.6 patch] add include/asm-avr32/xor.h Adrian Bunk
2008-04-14 18:11 ` Sebastian Siewior
2008-04-14 18:15 ` Adrian Bunk
2008-04-14 21:46 ` Sebastian Siewior
2008-04-14 21:50 ` Mike Frysinger
2008-04-14 22:01 ` Adrian Bunk
2008-04-14 22:11 ` Mike Frysinger
2008-04-14 22:27 ` Dan Williams
2008-04-14 22:30 ` Mike Frysinger [this message]
2008-04-14 23:45 ` Dan Williams
2008-04-15 0:47 ` Mike Frysinger
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=8bd0f97a0804141530i7c6ee03codeb0a546d333cb2f@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=bunk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hskinnemoen@atmel.com \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon.nelson@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