Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: nick.cheng@areca.com.tw
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] SCSI: Support Type C RAID controller
Date: Mon, 21 Jun 2010 09:16:29 -0500	[thread overview]
Message-ID: <1277129789.10998.17.camel@mulgrave.site> (raw)
In-Reply-To: <76AB9A4FE9D94F96B7F79FC2896CC46E@areca4e4f859d4>

On Mon, 2010-06-21 at 11:02 +0800, Nick Cheng wrote:
> 1. To support Type C RAID controller, ACB_ADAPTER_TYPE_C, i.e. PCI device
> ID: 0x1880.
> Signed-off-by: Nick Cheng< nick.cheng@areca.com.tw >

It's still giving the same rejections ... including the one I drew your
attention to in the header.  Either there's a patch missing somewhere,
or we're not working from the same base.  What I have is 2.6.35-rc3 plus
your patch 1/3 here

Message-id: <6D8C005181EA4A93BF2C281E4E1F72FC@areca4e4f859d4>

Let's try to come at this a different way since you don't seem to be
able to use git.  The current files I'm patching against are available
here (this includes your patch 1/3):

http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=tree;f=drivers/scsi/arcmsr

You can download them directly from the web using the "raw" link.  Can
you make sure the patches you send apply cleanly to these files?

James



  reply	other threads:[~2010-06-21 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  3:02 [PATCH 2/3] SCSI: Support Type C RAID controller Nick Cheng
2010-06-21 14:16 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-18  7:39 Nick Cheng
2010-06-20 14:18 ` James Bottomley
2010-05-26  4:55 Nick Cheng

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=1277129789.10998.17.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nick.cheng@areca.com.tw \
    /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