From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>,
"Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, git-dev@xilinx.com,
linux-kernel@vger.kernel.org, jirislaby@gmail.com
Subject: Re: [PATCH] [POWERPC] [v2] Xilinx: hwicap: cleanup
Date: Wed, 27 Feb 2008 11:20:02 -0700 [thread overview]
Message-ID: <fa686aa40802271020w4ebf05b0w6745e82cb4b51107@mail.gmail.com> (raw)
In-Reply-To: <20080224233457.C983D78006D@mail33-sin.bigfish.com>
On Sun, Feb 24, 2008 at 4:34 PM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
> Fix some missing __user tags and incorrect section tags.
> Convert semaphores to mutexes.
> Make probed_devices re-entrancy and error condition safe.
> Fix some backwards memcpys.
> Some other minor cleanups.
> Use kerneldoc format.
>
> [v2]
> __user char => char __user
> removed unused hwicap_command_capture
> Fixed a comment that didn't match the function name
> fixed argument with 'register' keyword.
>
>
> Signed-off-by: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Josh, can you please pick this up?
Thanks,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-02-27 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1202437061-12691-1-git-send-email-stephen.neuendorffer@xilinx.com>
2008-02-11 18:24 ` [PATCH] Xilinx: hwicap: cleanup Stephen Neuendorffer
2008-02-24 6:16 ` Grant Likely
2008-02-24 6:20 ` Grant Likely
2008-02-24 23:21 ` Stephen Neuendorffer
2008-02-24 23:34 ` [PATCH] [POWERPC] [v2] " Stephen Neuendorffer
2008-02-27 18:20 ` Grant Likely [this message]
2008-02-25 8:16 ` [PATCH] " Jiri Slaby
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=fa686aa40802271020w4ebf05b0w6745e82cb4b51107@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=git-dev@xilinx.com \
--cc=jirislaby@gmail.com \
--cc=jwboyer@linux.vnet.ibm.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).