From: Elias Oltmanns <eo@nebensachen.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ide: /proc/ide/hd*/settings rework
Date: Tue, 29 Jul 2008 17:43:55 +0200 [thread overview]
Message-ID: <87od4gn1ac.fsf@denkblock.local> (raw)
In-Reply-To: 20080727185602.4660.66530.sendpatchset@localhost.localdomain
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> Hi,
>
> I finally dusted off /proc/ide/hd*/settings rework (this has been laying
> on my hdd and waiting for the better days for at least 1.5 year, draft
> version even longer like ~3 years... sigh).
>
> The main motivation for doing it is that with infrastructure for private
> IDE subsystem requests from Elias Oltmanns (which was merged recently)
> and this patchset it should be possible (by using private requests for
> device settings) to make IDE locking code a lot saner and get rid of
> of ide_spin_wait_hwgroup()-ugliness completely.
>
> Elias if you would like to take care of it please go ahead [ from a quick
> look it seems this would mostly require adding new request type, pointing
> rq->special to setting's ->get or ->set method and putting setting's type
> (read/write -> 1 bit) + argument (int) somewhere inside request but you
> probably know better ].
Yes, I'll have a go at it. I haven't quite figured out yet whether I can
(or should, for that matter) get rid of drive->special and convert the
rest accordingly.
Anyway, I probably won't get it done before next week.
Regards,
Elias
prev parent reply other threads:[~2008-07-29 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 18:56 [PATCH 0/3] ide: /proc/ide/hd*/settings rework Bartlomiej Zolnierkiewicz
2008-07-27 18:56 ` [PATCH 1/3] ide: call ide_proc_register_driver() later Bartlomiej Zolnierkiewicz
2008-07-27 18:56 ` [PATCH 2/3] ide: preparations for /proc/ide/hd*/settings rework Bartlomiej Zolnierkiewicz
2008-07-27 18:56 ` [PATCH 3/3] ide: " Bartlomiej Zolnierkiewicz
2008-07-29 15:43 ` Elias Oltmanns [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=87od4gn1ac.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).