From: Chris Wedgwood <cw@f00f.org>
To: Matthias-Christian Ott <matthias.christian@tiscali.de>
Cc: Steve Lord <lord@xfs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Preempt & Xfs Question
Date: Thu, 27 Jan 2005 08:51:45 -0800 [thread overview]
Message-ID: <20050127165145.GA13181@taniwha.stupidest.org> (raw)
In-Reply-To: <41F931CD.5030401@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.
next prev parent reply other threads:[~2005-01-27 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 16:18 Matthias-Christian Ott
2005-01-27 15:29 ` Steve Lord
2005-01-27 15:40 ` Chris Wedgwood
2005-01-27 17:46 ` Matthias-Christian Ott
2005-01-27 15:53 ` Chris Wedgwood
2005-01-27 18:24 ` Matthias-Christian Ott
2005-01-27 16:51 ` Chris Wedgwood [this message]
2005-01-27 19:24 ` Matthias-Christian Ott
2005-01-27 21:11 ` Nathan Scott
2005-01-27 17:41 ` Matthias-Christian Ott
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=20050127165145.GA13181@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@xfs.org \
--cc=matthias.christian@tiscali.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®