[lkml]   [2006]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
    On Tue, Jan 10, 2006 at 08:07:56AM -0800, Bryan O'Sullivan wrote:

    > The only problem with this is that it's an unusual approach, so I don't
    > have any obvious examples to copy. The closest I can think of is
    > arch/x86_64/kernel/Makefile, which pulls in routines from the i386 tree
    > like this:
    > bootflag-y += ../../i386/kernel/bootflag.o
    > So say arch/ia64/lib/Makefile, for example, could have a line like this:
    > obj-y += ../../../lib/raw_memcpy_toio32.o
    > Sam, do you think this is safe to do in generalwith respect to kbuild?
    It is safe if you pull in .o files from a directory that you otherwise
    does not visit. But pulling in .o files that can/will be build
    by another Makkefile is doomed.

    But seeing other mails in this thread the final solution does not use
    this anyway.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-01-10 21:07    [W:0.020 / U:3.904 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site