From: Tony Battersby <tonyb@cybernetics.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: sym53c8xx patches for scsi-misc
Date: Fri, 27 Feb 2009 10:22:06 -0500 [thread overview]
Message-ID: <49A8051E.4050600@cybernetics.com> (raw)
James,
I posted a number of sym53c8xx patches back in early January that seem
to have been forgotten. Would you please add these to scsi-misc? Let
me know if you would prefer if I resend them instead of just posting
links to the archives.
http://marc.info/?l=linux-scsi&r=9&b=200901&w=4
[PATCH 0/7] sym53c8xx fixes
[PATCH 1/7] sym53c8xx: fix shost use-after-free and memory leak
[PATCH 2/7] sym53c8xx: fix NULL deref on error path
[PATCH 3/7] sym53c8xx: fix bogus free_irq() on error path
[PATCH 4/7] sym53c8xx: unmap pci memory after probe errors
[PATCH 5/7] sym53c8xx: handle pci_iomap() failures
[PATCH 6/7] sym53c8xx: use a queue depth of 1 for untagged devices
[PATCH 7/7] sym53c8xx: don't flood syslog with negotiation messages
The following patch was posted a year ago but forgotten. I have been
using it for a long time, and it still applies cleanly.
sym53c8xx ISTAT1 feature never set
http://marc.info/?t=120076464500006&r=1&w=4
http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg13352.html
Tested with my approval (be sure to use the updated version):
[PATCH] sym53c8xx_2: slave_alloc/destroy safety (2.6.27.5)
http://marc.info/?l=linux-scsi&m=123063187829449&w=4
Tested with my approval:
[PATCH] sym53c8xx_2: lun to_clear flag not re-initialized (2.6.27.5)
http://marc.info/?t=122710178300003&r=1&w=4
Thanks,
Tony Battersby
reply other threads:[~2009-02-27 15:22 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=49A8051E.4050600@cybernetics.com \
--to=tonyb@cybernetics.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@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.