linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@redhat.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org
Subject: Re: PATCH: switch ide-proc to use the ide_key functionality
Date: Mon, 16 Aug 2004 11:30:11 -0400	[thread overview]
Message-ID: <20040816153011.GE10279@devserv.devel.redhat.com> (raw)
In-Reply-To: <200408161724.09880.bzolnier@elka.pw.edu.pl>

On Mon, Aug 16, 2004 at 05:24:09PM +0200, Bartlomiej Zolnierkiewicz wrote:
> This patch removes write access to /proc/ide/hd?/driver without even
> mentioning this - IMHO we should deprecate it first.  Such changes should
> be described (with rationale for them) at least in the changelog
> (or even better in Documentation/ide.txt).

I thought we discussed this earlier - its essentially unfixable. You can
either have trivial /proc crashes, deadlocks on writing this file or lose
the feature (which nobody on the planet even knew about). 

If you've got any ideas how to fix it then let me know.

Agreed about adding it to Documentation/ide.txt

  reply	other threads:[~2004-08-16 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15 15:04 PATCH: switch ide-proc to use the ide_key functionality Alan Cox
2004-08-16 15:24 ` Bartlomiej Zolnierkiewicz
2004-08-16 15:30   ` Alan Cox [this message]
2004-08-16 23:22     ` Bartlomiej Zolnierkiewicz
2004-08-16 23:35 ` Bartlomiej Zolnierkiewicz
2004-08-17  0:13   ` Alan Cox
2004-08-17  0:31     ` Bartlomiej Zolnierkiewicz
2004-08-17  0:41       ` Alan Cox
2004-08-17  1:05       ` Alan Cox
2004-08-17 10:48         ` Bartlomiej Zolnierkiewicz
2004-08-17 12:06           ` Alan Cox
2004-08-17 22:15             ` Alan Cox

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=20040816153011.GE10279@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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).