linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Mark Robson <markxr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Proposal: block(4)
Date: Wed, 22 Sep 2010 09:57:02 -0400	[thread overview]
Message-ID: <20100922135702.GA19439@infradead.org> (raw)
In-Reply-To: <AANLkTin_m9n=X6k2S-8pDA_B6Z3sMt5ifYUjUG5wd_ab-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Sun, Sep 12, 2010 at 03:51:56PM +0100, Mark Robson wrote:
> Hi,
> 
> Looking at the sd(4) man page, there appear to be some BLK* ioctls
> documented, but these don't really belong here, as some of them apply to all
> block devices.
> 
> Should the common functions of a block device appear on a new page, block(4)
> and refer to hd(4), sd(4), ram(4) etc as necessary?
> 
> I would create one if there was some interest.

Yes, please do.  Besides the completely generic ioctls implemented in
blkdev_ioctl it would also be good to have a manpage for the "generic
scsi" ioctls in scsi_cmd_ioctl.

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-09-22 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 14:51 Proposal: block(4) Mark Robson
     [not found] ` <AANLkTin_m9n=X6k2S-8pDA_B6Z3sMt5ifYUjUG5wd_ab-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-22 13:57   ` Christoph Hellwig [this message]

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=20100922135702.GA19439@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=markxr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).