From: Greg KH <greg@kroah.com>
To: Michael Holzheu <HOLZHEU@de.ibm.com>
Cc: Ingo Oeser <ioe-lkml@rameria.de>,
linux-kernel@vger.kernel.org, mschwid2@de.ibm.com, pavel@ucw.cz,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: How to document dimension units for virtual files?
Date: Mon, 13 Nov 2006 09:16:12 -0800 [thread overview]
Message-ID: <20061113171612.GA14976@kroah.com> (raw)
In-Reply-To: <OF6928B06C.594331CB-ON41257222.0035C1AB-41257222.003747B5@de.ibm.com>
On Fri, Nov 10, 2006 at 11:03:48AM +0100, Michael Holzheu wrote:
> At least for our s390_hypfs I would like to use the suggested naming
> scheme. It is new and therefore not burdened with other naming
> conventions. Ok?
>
> So, no "Documentation/filesystems/ExportData" patch?
For now, I would not think so. Just document the file units in the
Documentation/ABI/ directory and you should be fine.
thanks,
greg k-h
next prev parent reply other threads:[~2006-11-13 17:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 16:54 How to document dimension units for virtual files? Michael Holzheu
2006-11-08 17:04 ` Randy Dunlap
2006-11-08 18:27 ` Michael Holzheu
2006-11-10 6:53 ` Greg KH
2006-11-10 10:03 ` Michael Holzheu
2006-11-13 17:16 ` Greg KH [this message]
2006-11-13 12:18 ` Pavel Machek
2006-11-13 17:46 ` Henrique de Moraes Holschuh
2006-11-14 8:50 ` Michael Holzheu
2006-11-08 17:09 ` Jörn Engel
2006-11-08 18:32 ` Michael Holzheu
2006-11-08 18:01 ` Henrique de Moraes Holschuh
2006-11-08 18:37 ` Michael Holzheu
2006-11-08 19:59 ` Henrique de Moraes Holschuh
2006-11-09 23:15 ` Pavel Machek
2006-11-10 13:18 ` Kyle Moffett
2006-11-10 15:41 ` Sanjoy Mahajan
2006-11-13 4:33 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 12:32 Michael Holzheu
2006-10-23 19:03 ` Ingo Oeser
2006-10-24 14:15 ` Michael Holzheu
2006-10-24 20:13 ` Arnd Bergmann
2006-10-28 18:40 ` Pavel Machek
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=20061113171612.GA14976@kroah.com \
--to=greg@kroah.com \
--cc=HOLZHEU@de.ibm.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@de.ibm.com \
--cc=pavel@ucw.cz \
--cc=randy.dunlap@oracle.com \
/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