From: Dan Carpenter <dan.carpenter@oracle.com>
To: 黃清隆 <ching2048@areca.com.tw>
Cc: James Bottomley <jbottomley@parallels.com>,
Tomas Henzl <thenzl@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1.0 14/16] arcmsr: fix sparse checking error
Date: Mon, 5 May 2014 15:10:36 +0300 [thread overview]
Message-ID: <20140505121036.GO4963@mwanda> (raw)
In-Reply-To: <CAKiknE-cJZpkpjMEPiX_cP4iC3e_b5huk2WJBvK2FpkKHecJoQ@mail.gmail.com>
On Mon, May 05, 2014 at 12:10:39PM +0800, 黃清隆 wrote:
> Hi Dan,
>
> In this patch, there are several replace of call readl() or writel()
> by direct access to memory.
> Because in main memory, we allocated a block of memory for
> post_qbuffer and done_qbuffer.
> These memory are access by both of CPU and IOP, they are not hardware registers.
> This change will not introduce a bug. I have verified it.
>
Oh yeah. I see that now. I got mixed up.
regards,
dan carpenter
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: 黃清隆 <ching2048@areca.com.tw>
Cc: James Bottomley <jbottomley@parallels.com>,
Tomas Henzl <thenzl@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1.0 14/16] arcmsr: fix sparse checking error
Date: Mon, 5 May 2014 15:10:36 +0300 [thread overview]
Message-ID: <20140505121036.GO4963@mwanda> (raw)
In-Reply-To: <CAKiknE-cJZpkpjMEPiX_cP4iC3e_b5huk2WJBvK2FpkKHecJoQ@mail.gmail.com>
On Mon, May 05, 2014 at 12:10:39PM +0800, 黃清隆 wrote:
> Hi Dan,
>
> In this patch, there are several replace of call readl() or writel()
> by direct access to memory.
> Because in main memory, we allocated a block of memory for
> post_qbuffer and done_qbuffer.
> These memory are access by both of CPU and IOP, they are not hardware registers.
> This change will not introduce a bug. I have verified it.
>
Oh yeah. I see that now. I got mixed up.
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-05 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 11:38 [PATCH v1.0 14/16] arcmsr: fix sparse checking error ching
2014-05-02 9:13 ` Dan Carpenter
2014-05-05 4:10 ` 黃清隆
2014-05-05 12:10 ` Dan Carpenter [this message]
2014-05-05 12:10 ` Dan Carpenter
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=20140505121036.GO4963@mwanda \
--to=dan.carpenter@oracle.com \
--cc=ching2048@areca.com.tw \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=thenzl@redhat.com \
/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.