All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: Markus Stockhausen <stockhausen@collogia.de>,
	Christoph Hellwig <hch@infradead.org>
Cc: "ching2048@areca.com.tw" <ching2048@areca.com.tw>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: AW: ARCMSR - Notify sense data report - Lost patch?
Date: Mon, 24 Nov 2014 15:47:56 +0100	[thread overview]
Message-ID: <5473451C.1040400@redhat.com> (raw)
In-Reply-To: <12EF8D94C6F8734FB2FF37B9FBEDD1735F8C20B0@EXCHANGE.collogia.de>

On 11/24/2014 02:45 PM, Markus Stockhausen wrote:
>> Von: linux-scsi-owner@vger.kernel.org [linux-scsi-owner@vger.kernel.org]&quot; im Auftrag von &quot;Christoph Hellwig [hch@infradead.org]
>> Gesendet: Montag, 24. November 2014 14:23
>> An: Markus Stockhausen
>> Cc: ching2048@areca.com.tw; thenzl@redhat.com; linux-scsi@vger.kernel.org
>> Betreff: Re: ARCMSR - Notify sense data report - Lost patch?
>>
>> On Mon, Nov 24, 2014 at 11:47:02AM +0000, Markus Stockhausen wrote:
>>> Hi,
>>>
>>> sorting out some diffs between the official Arcea driver and
>>> the newest 3.18 patches I found a patch that might got lost:
>>>
>>> https://lkml.org/lkml/2014/2/20/956
>>>
>>> Could you check if that is desired?
>> Looks sensible to me.  Did you test it?
> No not really, as I don't know how. We had a controller crash the last
> week and I was wondering about the differences between vendor and
> upstream version. So I basically did some code comparison between 
> the two source. Besides a lot of layout differences and other hacks 
> this was one of the first things I noticed and wondered what difference 
> those flags could make. Especially regarding stability.
>
> Hopefully Ching and/or Tomas know better as they seem repsonsible 
> for the rest of the 3.18 arcmsr patches.

I don't know why Ching hasn't re-posted this in later series.
The Areca in-house driver works stable?

>
> Markus


  reply	other threads:[~2014-11-24 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 11:47 ARCMSR - Notify sense data report - Lost patch? Markus Stockhausen
2014-11-24 13:23 ` Christoph Hellwig
2014-11-24 13:45   ` AW: " Markus Stockhausen
2014-11-24 14:47     ` Tomas Henzl [this message]
2014-11-24 18:25       ` AW: " Markus Stockhausen
     [not found]         ` <CAKiknE87ac0yKzrvgiRj5fnq7OvdJSeVgYBLjt=rFYkjfS1yZg@mail.gmail.com>
2014-11-26 17:46           ` Markus Stockhausen
2014-11-27 11:43             ` 黃清隆
2014-11-27 16:05               ` AW: " Markus Stockhausen
2014-11-28  2:36                 ` 黃清隆

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=5473451C.1040400@redhat.com \
    --to=thenzl@redhat.com \
    --cc=ching2048@areca.com.tw \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stockhausen@collogia.de \
    /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.