Re: x86: Why have __copy_from_user_ll_nocache* been exported?
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Thu, 31 Jan 2008 22:18:17 +0100
* Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
A commit that does nothing except for adding two unused
EXPORT_SYMBOL's.
Without any rationale why they should be exported.
Don't look at me. This has been sitting in my tree for nearly two
years as part of the reiser4 patchset. It may not even be needed any
more. I guess Ingo went on a fishing expedition and liked the change.
yes, i picked it up from -mm (as can be seen from the SOB line), and i
agreed with that change regardless of the reiser4 patchset. (which might
never see the light of upstream acceptance)
there's nothing more annoying than incomplete and inconsistent APIs. I'm
trying to fix them up everywhere i see, and this is one of those cases.
Adrian still has not given any rationale about why he wants to see the
export removed.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- x86: Why have __copy_from_user_ll_nocache* been exported?
- From: Adrian Bunk
- Re: x86: Why have __copy_from_user_ll_nocache* been exported?
- From: Andrew Morton
- x86: Why have __copy_from_user_ll_nocache* been exported?
- Prev by Date: Re: [RFC] Default child of a cgroup
- Next by Date: Re: Purpose of numa_node?
- Previous by thread: Re: x86: Why have __copy_from_user_ll_nocache* been exported?
- Next by thread: [PATCH] nozomi: constify driver
- Index(es):
Relevant Pages
|
|