From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHWORK] 71715 -> Not applicable.
Date: Fri, 19 Nov 2010 11:50:20 +0100 [thread overview]
Message-ID: <4CE6566C.4020202@free.fr> (raw)
In-Reply-To: <201011190213.07089.vapier@gentoo.org>
Le 19/11/2010 08:13, Mike Frysinger a ?crit :
> On Friday, November 19, 2010 00:59:47 Albert ARIBAUD wrote:
>> Le 19/11/2010 00:13, Mike Frysinger a ?crit :
>>> On Thursday, November 18, 2010 17:21:49 Albert ARIBAUD wrote:
>>>> Besides, about half the archs do not use asm-generic/unaligned, and half
>>>> do
>>>
>>> that's because half the arches implemented unaligned.h whilst only
>>> thinking of themselves. the other half benefited from my work of
>>> thinking of everyone.
>>>
>>>> a resubmit on the list will be the occasion
>>>
>>> i dont use/care about arm. i wrote the patch because i wanted to be
>>> nice. if you cant be bothered to clean up arm cruft, then feel free to
>>> mark the patch as "pending due to maintainer laziness".
>>>
>>>> for example, to discuss whether all arches should use it.
>>>
>>> all arches should use it. whether the maintainers can be bothered to fix
>>> their headers is a different question.
>>
>> My question was about the technical merits of the patch: why should all
>> arches use it? What does it improve at a performance, maintenability, or
>> other technical level ?
>
> obviously maintenance is improved since only one header needs to be maintained
> and it isnt an arm one
> -mike
Maintenance being about changes, I did a git log on both
include/asm-generic/unaligned.h and arch/arm/include/asm/unaligned.h.
Each has exactly one commit: the generic one when creating the file, the
arm one when the directories were rearranged. Very little changes either
way.
I do understand the benefit in overall maintenability of having a common
situation for all archs. But I don't think there is an increase of
maintenability per se in, basically, adding a level of #include.
If the goal is 'have all arches use a single unaligned.h' -- then fine,
let us *remove* the unaligned.h files in arches and refer to the generic
one instead. That, indeed, would increase maintenability by *reducing*
the number of files while *not* adding any complexity. I'll happily ack
such a change.
In any case, this is not specifically an 'arm' topic: it touches all
arches albeit lightly -- as you point out, Mike, this is a generic
change. So I'd rather see a patchset to fix this globally and for good
for every arch.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-11-19 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 21:31 [U-Boot] [PATCHWORK] 71715 -> Not applicable Albert ARIBAUD
2010-11-18 21:50 ` Wolfgang Denk
2010-11-18 22:00 ` Mike Frysinger
2010-11-18 22:21 ` Albert ARIBAUD
2010-11-18 23:13 ` Mike Frysinger
2010-11-19 5:59 ` Albert ARIBAUD
2010-11-19 7:13 ` Mike Frysinger
2010-11-19 10:50 ` Albert ARIBAUD [this message]
2010-11-19 10:51 ` Mike Frysinger
2010-11-19 11:56 ` Albert ARIBAUD
2010-11-20 8:36 ` 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=4CE6566C.4020202@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/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.