linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: dave.jiang@intel.com, linux-scsi@vger.kernel.org,
	jacek.danecki@intel.com, ed.ciechanowski@intel.com,
	jeffrey.d.skirvin@intel.com, edmund.nadolski@intel.com
Subject: Re: [PATCH 2/2] isci: remove base_request abstraction
Date: Thu, 31 Mar 2011 15:14:14 -0700	[thread overview]
Message-ID: <AANLkTinTFY69L67u2qZpyUWmDOqGFy7ePMdwb2dVWFKi@mail.gmail.com> (raw)
In-Reply-To: <20110328132114.GB11684@infradead.org>

On Mon, Mar 28, 2011 at 6:21 AM, Christoph Hellwig <hch@infradead.org> wrote:
> Merge struct sci_base_request into scic_sds_request, and also factor the two
> types of state machine handlers into one function.  While we're at it also
> remove lots of duplicate incorrect kerneldoc comments for the state machine
> handlers.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>

Applied, thanks.

We'll want to do a tree-wide s/sci_base_/sci_/, but maybe not until we
settle on the final unified object names... put it off for now.

--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-03-31 22:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  0:07 [PATCH] scic: remove mmio wrappers Christoph Hellwig
2011-03-28 13:20 ` [PATCH, RFC 0/2] scic: remove pointless stuctures Christoph Hellwig
2011-03-28 13:21   ` [PATCH 1/2] isci: remove base_controller abstraction Christoph Hellwig
2011-03-31 21:21     ` Dan Williams
2011-03-28 13:21   ` [PATCH 2/2] isci: remove base_request abstraction Christoph Hellwig
2011-03-31 22:14     ` Dan Williams [this message]
2011-04-01 13:11       ` Christoph Hellwig
2011-03-31 22:24   ` [PATCH, RFC 0/2] scic: remove pointless stuctures Dan Williams
2011-03-31  1:43 ` [PATCH] scic: remove mmio wrappers Dan Williams
2011-03-31  6:31   ` Christoph Hellwig

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=AANLkTinTFY69L67u2qZpyUWmDOqGFy7ePMdwb2dVWFKi@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=edmund.nadolski@intel.com \
    --cc=hch@infradead.org \
    --cc=jacek.danecki@intel.com \
    --cc=jeffrey.d.skirvin@intel.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 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).