public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.5.19 IDE 76
Date: Fri, 31 May 2002 13:09:04 +0200	[thread overview]
Message-ID: <3CF759D0.5030208@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205291146510.1344-100000@penguin.transmeta.com>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

Wed May 29 19:02:15 CEST 2002 ide-clean-76

- Since Bartek has released finally an entierly user space based setup
    monitoring utility, we can finally remove the nonfunctional PROC code from
    the host chip drivers. We have preserved it thus far only for documentation
    purposes.

- Use generic bus master DMA setup code. There is nothing wrong with it.

- Make the ide-scsi code actually just allow for one device id per scsi host,
    since we are registering a host per device right now.  This prevents the
    repetitive device recognition. Well registering an SCSI host of every single
    disk out there isn't the proper thing to do. I will deal with that later
    after my visual perception recovers again from already looking too long at
    the SCSI code :-).

- Deal properly with host specific data mapping. (Could be that solves some
    problems with the driver, which where in reality kernel data corruptions.)

- Homogenize flag handling for ATAPI drivers.


[-- Attachment #2: ide-clean-76.diff.gz --]
[-- Type: application/x-gzip, Size: 17516 bytes --]

  parent reply	other threads:[~2002-05-31 12:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 18:50 Linux 2.5.19 Linus Torvalds
2002-05-29 19:42 ` Jason Lunz
2002-05-29 20:17 ` Russell King
2002-05-29 20:38   ` Eli Carter
2002-05-29 20:44   ` James Simmons
2002-05-29 20:47     ` Russell King
2002-05-29 22:22       ` Martin Dalecki
2002-05-29 23:25         ` Russell King
2002-05-29 22:42           ` Martin Dalecki
2002-05-29 23:52             ` Russell King
2002-05-29 23:00               ` Martin Dalecki
2002-05-29 22:43       ` James Simmons
2002-05-29 22:29         ` Martin Dalecki
2002-05-29 23:31           ` Russell King
2002-05-30  5:10             ` Framebuffer policy [ was Re: Linux 2.5.19] James Simmons
2002-05-29 20:37 ` [PATCH] Missing include in drivers/base/bus.c and drivers/pci/pci-driver.c Tom Rini
2002-05-29 22:24 ` Linux 2.5.19 Tom Rini
2002-05-30  1:29   ` Rusty Russell
2002-05-29 23:01 ` Matthias Andree
2002-05-29 23:35 ` J.A. Magallon
2002-05-30 14:15 ` [PATCH] 2.5.19 blk.h and more about the ugly kids Martin Dalecki
2002-05-31 11:09 ` Martin Dalecki [this message]
2002-05-31 18:17 ` [PATCH] 2.5.19 IDE 77 Martin Dalecki
2002-06-02  6:04 ` [PATCH] 2.5.19 IDE 78 Martin Dalecki
2002-06-02  8:16   ` Paul Dickson
2002-06-02  9:21   ` Paul Mackerras
2002-06-02 19:34     ` Martin Dalecki
2002-06-02 21:36       ` Bartlomiej Zolnierkiewicz
2002-06-02 21:59       ` Paul Mackerras
2002-06-03  4:47         ` Martin Dalecki
2002-06-02  6:06 ` [PATCH} 2.5.19 IDE 79 Martin Dalecki
2002-06-02  6:07 ` [PATCH] 2.5.19 IDE 80 Martin Dalecki
2002-06-02 19:45 ` [PATCH] 2.5.19 IDE 81 Martin Dalecki
2002-06-02 20:13 ` [PATCH] 2.5.19 IDE 82 Martin Dalecki

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=3CF759D0.5030208@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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