linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: lsf10-pc@lists.linuxfoundation.org
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-ide <linux-ide@vger.kernel.org>
Subject: [LSF/MM ATTEND] discussion around bettter SAS/SATA integration
Date: Sat, 29 Jan 2011 09:53:39 -0800	[thread overview]
Message-ID: <1296323619.3020.19.camel@mulgrave.site> (raw)

I'm not sure it will be a whole topic (or rather I suspect others want
to present on this), but I'd like to discuss better SAS/SATA
integration.  Right at the moment, I think we're getting close to
agreement on how to integrate the new error handler into libsas ...
we're still further off on the other consumer: ipr.  However, trying to
integrate libsas into the libata transport class hierarchy is proving
challenging (read it keep crashing), so I'd like to spend some time with
the interested parties trying to make all this work.

James



                 reply	other threads:[~2011-01-29 17:53 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=1296323619.3020.19.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf10-pc@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).