Re: Preempt & Xfs Question

From: Chris Wedgwood (cw_at_f00f.org)
Date: 01/27/05

  • Next message: Marc: "Re: critical bugs in md raid5" 
    Date:	Thu, 27 Jan 2005 08:51:45 -0800
To: Matthias-Christian Ott <matthias.christian@tiscali.de>

    On Thu, Jan 27, 2005 at 06:24:13PM +0000, Matthias-Christian Ott wrote:

    > Well calling such a internal function (__function) is not a cleaning
    > coding style but works best :-) .

    __foo does NOT mean it's an internal function necessarily or that it's
    unclean to use it (sadly Linux has pretty vague (nothing consistent)
    rules on how to interpret __foo versus foo really.

    > Combined with the current_cpu() fixes I mentioned, it looks like
    > this:

    (1) your patch is mangled/wrapped

    (2) this is fixed in CVS already (for maybe a week or so now?)

    > I'll submit it to the mailinglist as a seperate patch, so Linus can
    > apply it to the current Kernel.

    XFS patches/suggestions should go to linux-xfs@oss.sgi.com and the
    maintainers there can comment as needed.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Marc: "Re: critical bugs in md raid5"

    Relevant Pages