public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Roger Gammans <roger@computer-surgery.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: fs/bio.c - Hardcoded sector size ?
Date: Fri, 29 Sep 2006 12:37:37 -0700	[thread overview]
Message-ID: <20060929123737.ec613178.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060928191946.GC4759@julia.computer-surgery.co.uk>

On Thu, 28 Sep 2006 20:19:46 +0100 Roger Gammans wrote:

> On Fri, Sep 29, 2006 at 12:11:57PM -0700, Randy Dunlap wrote:
> > I don't know if or where it is documented.
> 
> Well, I've spend a good chunk of time reading round this part of
> the kernel's interfaces without spotting it so another note somewhere
> can't help.
> 
> > You can submit a patch for it.
> > If you don't, I'll put it in my todo queue.
> 
> If I find an approriate place to put such a note I'll add it and
> submit a patch, but I'm not sure where to put it , atm.
> 
> Any suggestions?

Hm, I looked thru fs/bio.c and block/*.c and Documentation/Docbook/*.tmpl.
The best place that I see to put it right now is in
include/linux/bio.h, struct bio, field: bi_sector.

What do you think of that?
---
~Randy
GPL v0:  http://www.glacierparkinc.com/GlacierParkLodge.htm

  reply	other threads:[~2006-09-29 19:36 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 [this message]
2006-09-28 19:56           ` Roger Gammans
2006-09-29 20:17             ` Randy Dunlap
2006-09-29 20:22               ` Zach Brown
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=20060929123737.ec613178.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --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