From: Gabriel C <nix.or.die@googlemail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi@vger.kernel.org
Subject: Re: Someone ( bsg merge ? ) broke {sd,hd}parm on current git
Date: Tue, 17 Jul 2007 02:44:38 +0200 [thread overview]
Message-ID: <469C10F6.3050008@googlemail.com> (raw)
In-Reply-To: <469BD9C8.4000808@googlemail.com>
Gabriel C wrote:
> Hello,
>
> sdparm and hdparm are broken for me on git (
> abce891a10559343d8ac9f79b46d78afdba63a40 )
>
>
> ~$ sudo hdparm /dev/sdc
>
> /dev/sdc:
> BLKROGET failed: Inappropriate ioctl for device
> BLKRAGET failed: Inappropriate ioctl for device
> BLKGETSIZE failed: Inappropriate ioctl for device
>
>
> ~$ sudo sdparm --all /dev/sdc
> unable to access /dev/sdc, ATA disk?
>
>
Well it is bsg , setting BLK_DEV_BSG=n fixed all this errors.
Maybe a bit off topic but it depends on EXPERIMENTAL so why the the menu
is not telling this ? and why the default is 'y' for it ?
IMO everything depends on EXPERIMENTAL should
1) Tell it is EXPERIMENTAL ( visible to the user in menu ) " Foo New
stuff ( EXPERIMENTAL ) "
2) Should not default to 'y' , is up to the users/admins to set
EXPERIMENTAL things to Y/M , isn't it ?
( PS: there are even defconfigs with EXPERIMENTAL things set to y but
this is really off topic )
Regards,
Gabriel C
next parent reply other threads:[~2007-07-17 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <469BD9C8.4000808@googlemail.com>
2007-07-17 0:44 ` Gabriel C [this message]
2007-07-17 1:09 ` Someone ( bsg merge ? ) broke {sd,hd}parm on current git FUJITA Tomonori
2007-07-17 1:40 ` Gabriel C
2007-07-18 23:25 ` FUJITA Tomonori
2007-07-19 0:48 ` Gabriel C
2007-07-19 14:02 ` James Bottomley
2007-07-19 14:31 ` Gabriel C
2007-07-19 15:19 ` James Bottomley
2007-07-19 15:48 ` Gabriel C
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=469C10F6.3050008@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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).