From: Doug Ledford <dledford@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>,
Linux Scsi Mailing List <linux-scsi@vger.kernel.org>
Subject: Updates pushed to bk://linux-scsi.bkbits.net/scsi-dledford
Date: Fri, 20 Dec 2002 21:13:34 -0500 [thread overview]
Message-ID: <20021221021334.GD6554@redhat.com> (raw)
I grabbed the one change from James' tree and then committed my local
changes and shoved them all up to $SUBJECT location. There will be more
shortly from Luben, but these are ready to go any time. Here's the bk
changes -L report:
[dledford@flossy linus-2.5]$ bk changes -L bk://linux.bkbits.net/linux-2.5
ChangeSet@1.905, 2002-12-20 21:01:03-05:00, dledford@flossy.devel.redhat.com
aic7xxx_old/aic7xxx.h: Run time warning fix
ChangeSet@1.904, 2002-12-20 21:00:06-05:00, dledford@flossy.devel.redhat.com
Change all uses of device->request_queue (was struct, now pointer)
Update scsi_scan so that we don't pass around a scsi_device struct for
scanning. Instead, we pass around a request_queue during
scanning and create and destroy device structs as needed. This
allows us to have a 1:1 correlation between scsi_alloc_sdev()
and scsi_free_sdev() calls, which we didn't have before.
ChangeSet@1.903, 2002-12-20 20:54:35-05:00, dledford@flossy.devel.redhat.com
aic7xxx_old: improve usage of pci_request_regions due to device contention
ChangeSet@1.902, 2002-12-20 11:04:51-06:00, jejb@mulgrave.(none)
correct compile warnings without Large Block Device support
Based on a patch from Andrew Morton.
Also checks to see if the sd device is bigger than the kernel can
support and prints out a warning in that case
[dledford@flossy linus-2.5]$
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
reply other threads:[~2002-12-21 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021221021334.GD6554@redhat.com \
--to=dledford@redhat.com \
--cc=linux-scsi@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 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.