From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-dev@ozlabs.org, git-dev@xilinx.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Xilinx: hwicap: Refactor status handling code.
Date: Mon, 17 Mar 2008 14:23:02 -0600 [thread overview]
Message-ID: <fa686aa40803171323r2e73e53xd01d0590efccbf90@mail.gmail.com> (raw)
In-Reply-To: <20080317173644.C24651C00069@mail59-sin.bigfish.com>
On Mon, Mar 17, 2008 at 11:36 AM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
> Both the buffer-based and fifo-based icap cores have a status
> register. Previously, this was only used internally to check whether
> transactions have completed. However, the status can be useful to the
> main driver as well. This patch exposes these status functions to the
> main driver along with some masks for the differnet bits.
>
> Signed-off-by: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-03-17 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1205775392-32222-1-git-send-email-stephen.neuendorffer@xilinx.com>
2008-03-17 17:36 ` [PATCH 1/3] Xilinx: hwicap: Refactor status handling code Stephen Neuendorffer
2008-03-17 20:23 ` Grant Likely [this message]
[not found] ` <1205775392-32222-2-git-send-email-stephen.neuendorffer@xilinx.com>
2008-03-17 17:36 ` [PATCH 2/3] Xilinx: hwicap: Verify sync before reading idcode Stephen Neuendorffer
2008-03-17 20:18 ` Grant Likely
[not found] ` <1205775392-32222-3-git-send-email-stephen.neuendorffer@xilinx.com>
2008-03-17 17:36 ` [PATCH 3/3] Xilinx: hwicap: Use fixed device major Stephen Neuendorffer
2008-03-17 20:20 ` Grant Likely
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=fa686aa40803171323r2e73e53xd01d0590efccbf90@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=git-dev@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=stephen.neuendorffer@xilinx.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 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).