All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henne <henne@nachtwindheim.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] New idea for TODO
Date: Tue, 05 Sep 2006 21:59:59 +0000	[thread overview]
Message-ID: <44FDF35F.6090503@nachtwindheim.de> (raw)
In-Reply-To: <44FDD881.8070002@nachtwindheim.de>

>> I know that the TODO list is long, but I may have found a new task.
>>
>> In drivers/scsi lies a file called scsi.h which seems to be a relict and is included in many mature scsi-drivers,
>> but include/scsi/scsi.h would be the better choice.
>> After a little surfing I think all typedef'd Scsi_Cmnd can be replaced with struct scsi_cmnd, to get rid of
>> that typedef stuff.
>>
>> Correct me if I'm wrong.
> 
> include/scsi/scsi.h says:
> 
> /*
>  * NOTE:  this file only contains compatibility glue for old drivers.  All
>  * these wrappers will be removed sooner or later.  For new code please use
>  * the interfaces declared in the headers in include/scsi/
>  */
> 
> The file is already nearly empty, and the goal is getting it completely 
> empty, not moving the remaining stuff to a different header.

Thats what I meant, but I think I don't wrote it, right?
I wanted to say:
- change Scsi_Cmnd to struct scsi_cmnd in all drivers
- delete the include "scsi_typedefs.h" from drivers/scsi.h and
- remove drivers/scsi_typedefs.h from the tree

Don't ask me why I didn't wrote it in my first mail. :)

Greets,
Henne
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-09-05 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 20:05 [KJ] New idea for TODO Henne
2006-09-05 20:56 ` Adrian Bunk
2006-09-05 21:59 ` Henne [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=44FDF35F.6090503@nachtwindheim.de \
    --to=henne@nachtwindheim.de \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.