From: Zach Brown <zab@zabbo.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Roger Gammans <roger@computer-surgery.co.uk>,
lkml <linux-kernel@vger.kernel.org>,
axboe@kernel.dk
Subject: Re: fs/bio.c - Hardcoded sector size ?
Date: Fri, 29 Sep 2006 13:22:34 -0700 [thread overview]
Message-ID: <451D808A.9050005@zabbo.net> (raw)
In-Reply-To: <20060929131730.0b733137.rdunlap@xenotime.net>
> sector_t bi_sector; /* block layer sector
> * addresses are always in
> * 512-byte units in Linux */
How about adding kerneldoc for sector_t itself?
- z
next prev parent reply other threads:[~2006-09-29 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:22 fs/bio.c - Hardcoded sector size ? Roger Gammans
2006-09-29 18:38 ` Randy Dunlap
2006-09-28 18:58 ` linux-kernel-owner
2006-09-29 19:11 ` Randy Dunlap
2006-09-28 19:19 ` Roger Gammans
2006-09-29 19:37 ` Randy Dunlap
2006-09-28 19:56 ` Roger Gammans
2006-09-29 20:17 ` Randy Dunlap
2006-09-29 20:22 ` Zach Brown [this message]
2006-09-29 20:32 ` Randy Dunlap
2006-09-29 17:25 ` Roger Gammans
2006-09-30 19:31 ` Jens Axboe
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=451D808A.9050005@zabbo.net \
--to=zab@zabbo.net \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=roger@computer-surgery.co.uk \
/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