From: Andi Kleen <ak@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Andrew Morton <akpm@digeo.com>, Andrea Arcangeli <andrea@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
linux-mm@kvack.org
Subject: Re: New version of frlock (now called seqlock)
Date: Fri, 31 Jan 2003 00:51:42 +0100 [thread overview]
Message-ID: <20030130235142.GA32738@wotan.suse.de> (raw)
In-Reply-To: <1043969416.10155.619.camel@dell_ss3.pdx.osdl.net>
I noticed that a lot of functions are called seq_* now.
But we already have a seq_* family - Al Viro's seq_files,
which also have lots of seq_* functions.
Perhaps it would be better to call it seqlock_* to avoid confusion.
Sorry for be annoying.
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2003-01-30 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 23:30 Stephen Hemminger
2003-01-30 23:44 ` Andrew Morton
2003-01-30 23:50 ` Andrea Arcangeli
2003-01-31 0:15 ` Stephen Hemminger
2003-01-30 23:51 ` Andi Kleen [this message]
2003-01-31 0:33 ` Stephen Hemminger
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=20030130235142.GA32738@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=shemminger@osdl.org \
/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