From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Mark Hounschell <markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>,
"linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org >> SCSI
development list"
<linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: BUG: SCSI aic7xxx driver and AMD IOMMU
Date: Thu, 26 Mar 2015 13:45:59 +0100 [thread overview]
Message-ID: <20150326124559.GV4441@8bytes.org> (raw)
In-Reply-To: <5512E412.9040807-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
On Wed, Mar 25, 2015 at 12:36:34PM -0400, Mark Hounschell wrote:
> BTW, so far the first 2 patches are working well. I was going to
> wait until the end of the day to report but so far I have been
> unable to produce the problems I was seeing. And I am in the middle
> of some driver work so lots of unloading/loading going on.
Great, thanks. Please let me know when you have test results for the
other patches too.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Mark Hounschell <markh@compro.net>
Cc: iommu@lists.linux-foundation.org, Hannes Reinecke <hare@suse.de>,
"linux-scsi@vger.kernel.org >> SCSI development list"
<linux-scsi@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: SCSI aic7xxx driver and AMD IOMMU
Date: Thu, 26 Mar 2015 13:45:59 +0100 [thread overview]
Message-ID: <20150326124559.GV4441@8bytes.org> (raw)
In-Reply-To: <5512E412.9040807@compro.net>
On Wed, Mar 25, 2015 at 12:36:34PM -0400, Mark Hounschell wrote:
> BTW, so far the first 2 patches are working well. I was going to
> wait until the end of the day to report but so far I have been
> unable to produce the problems I was seeing. And I am in the middle
> of some driver work so lots of unloading/loading going on.
Great, thanks. Please let me know when you have test results for the
other patches too.
Joerg
next prev parent reply other threads:[~2015-03-26 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 14:34 BUG: SCSI aic7xxx driver and AMD IOMMU Mark Hounschell
[not found] ` <54E1FFFA.1060403-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2015-03-03 19:36 ` Mark Hounschell
2015-03-03 19:36 ` Mark Hounschell
2015-03-23 15:03 ` Joerg Roedel
[not found] ` <20150323150304.GQ4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-24 11:57 ` Mark Hounschell
2015-03-24 11:57 ` Mark Hounschell
2015-03-25 13:59 ` Joerg Roedel
[not found] ` <20150325135937.GR4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-25 15:13 ` Joerg Roedel
2015-03-25 15:13 ` Joerg Roedel
2015-03-25 16:36 ` Mark Hounschell
[not found] ` <5512E412.9040807-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2015-03-26 12:45 ` Joerg Roedel [this message]
2015-03-26 12:45 ` Joerg Roedel
2015-03-26 14:58 ` Mark Hounschell
2015-03-26 15:52 ` Joerg Roedel
[not found] ` <20150326155248.GW4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-26 17:09 ` Mark Hounschell
2015-03-26 17:09 ` Mark Hounschell
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=20150326124559.GV4441@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=hare-l3A5Bk7waGM@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.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.