The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/2] IDE CD more STANDARD_ATAPI ifdef
Date: Tue, 14 Jun 2005 09:43:14 +0200	[thread overview]
Message-ID: <42AE8A92.2040305@tremplin-utc.net> (raw)
In-Reply-To: <20050614054947.GC1484@suse.de>

14.06.2005 07:49, Jens Axboe wrote/a écrit:
> On Tue, Jun 14 2005, Eric Piel wrote:
>>This little patch adds more ifdef's to surround code not necessary for 
>>the standard ATAPI drives. I've tried to find all the code that was 
>>handling special cases. It reduces slightly more the module size :-) As 
>>most of the non standard drives handled seem quite old, this is very safe.
>>
>>This patch has to be applied after my previous patch 
>>(ide-cd-2.6.12-report-current-speed.patch) but I can remake it directly 
>>against latest vanilla kernel if you prefer. BTW, I'd like to make a 
>>Kconfig option for STANDARD_ATAPI, would you accept it?
> 
> 
> To be honest, I'd rather remove the STANDARD_ATAPI ifdef instead. It's
> really not a lot of code, and the ifdefs are just cluttering it up. BTW,
> if we were to honor STANDARD_ATAPI completely (ie strictly follow the
> spec), there would be far more outside of such an ifdef. It's pretty
> much an illusion and hasn't been followed for at least the last 5 years.
> 

Ok. That's a pity though, I discovered this option last week and was so 
happy to reduce the driver size of my little cute standard ATAPI drive 
;-) Well... then let's do the contrary: would accept a patch which 
remove every occurence of STANDARD_ATAPI ? :-)

Eric

      reply	other threads:[~2005-06-14  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 22:34 [PATCH] [2/2] IDE CD more STANDARD_ATAPI ifdef Eric Piel
2005-06-14  5:49 ` Jens Axboe
2005-06-14  7:43   ` Eric Piel [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=42AE8A92.2040305@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=axboe@suse.de \
    --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