public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clipped disk reports clipped lba size
Date: Sat, 02 Feb 2002 06:11:29 -0500	[thread overview]
Message-ID: <3C5BC961.6282BB7F@yahoo.com> (raw)
In-Reply-To: <UTC200202012155.VAA123193.aeb@cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> 
>     From: Paul Gortmaker <p_gortmaker@yahoo.com>
>
>     Alan has said (quite reasonably) that he is not interested in inclusion
>     of the big IDE patch that exists for 2.2.x -- however, a minimal cut and
>     paste backport from 2.4.x IDE to just support HDIO_DRIVE_CMD_AEB (and thus
>     support setmax) is only about a 100 line diff which I did a while ago.
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^
>     If there is any interest in this I can check it still applies cleanly to
>     current 2.2 pre kernel and send it along for inclusion.
> 
> (1) *_AEB is intended as private namespace for me, not for inclusion
> in an official kernel. So, some official name, like HDIO_DRIVE_TASK,
> must be better.

Yes, DRIVE_TASK is of course the official name - I just knew you would
immediately recognize *_AEB  & and know context/usage :)   BTW, if you
didn't want it in an official kernel, it is a bit late for that. It has
been in for some time in 2.4 .... <grep>  2.3.99pre9 to be exact.

> Both problems can be solved with relatively small patches,
> no big monolithic IDE patch required. And I would prefer

Please see above - I agree, and was suggesting a small patch to 2.2 
rather than the massive one (which Alan already ruled out months ago).

> to solve both problems without involving ioctl's, or boot
> parameters, or config parameters. All should just work
> in the common case.

This is a valid point - in an ideal situation things should just work
without user intervention or setmax util, etc.  What are you currently
recommending to 2.2.x kernel users that come across this limitation
prior to such an ideal fix being released in a 2.2.x kernel?

Paul.


  parent reply	other threads:[~2002-02-02 11:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 21:55 [PATCH] clipped disk reports clipped lba size Andries.Brouwer
2002-02-02  0:20 ` Andre Hedrick
2002-02-02 11:11 ` Paul Gortmaker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-02 13:38 Andries.Brouwer
2002-01-30 20:12 Andries.Brouwer
2002-02-01 12:10 ` Paul Gortmaker
2002-01-30 15:02 Eduardo Trápani
2002-01-30 15:34 ` Alan Cox
2002-01-30 17:04 ` Andre Hedrick

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=3C5BC961.6282BB7F@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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