From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-media@vger.kernel.org, andrzej.p@samsung.com,
s.nawrocki@samsung.com, patches@linaro.org
Subject: Re: [PATCH 1/2] [media] s5p-jpeg: Use spinlock_t instead of 'struct spinlock'
Date: Tue, 01 Jan 2013 19:21:52 +0100 [thread overview]
Message-ID: <50E32940.80903@gmail.com> (raw)
In-Reply-To: <1356690044-8694-1-git-send-email-sachin.kamat@linaro.org>
Hi Sachin,
On 12/28/2012 11:20 AM, Sachin Kamat wrote:
> Silences the following checkpatch warning:
> WARNING: struct spinlock should be spinlock_t
>
> Signed-off-by: Sachin Kamat<sachin.kamat@linaro.org>
> ---
> drivers/media/platform/s5p-jpeg/jpeg-core.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/media/platform/s5p-jpeg/jpeg-core.h b/drivers/media/platform/s5p-jpeg/jpeg-core.h
> index 022b9b9..8a4013e 100644
> --- a/drivers/media/platform/s5p-jpeg/jpeg-core.h
> +++ b/drivers/media/platform/s5p-jpeg/jpeg-core.h
> @@ -62,7 +62,7 @@
> */
> struct s5p_jpeg {
> struct mutex lock;
> - struct spinlock slock;
> + spinlock_t slock;
Thank you for these two patches, however there are already similar ones
applied in the media tree:
http://git.linuxtv.org/media_tree.git/commit/a75831f3600c479054fc3f70cd11257ab07886e2
http://git.linuxtv.org/media_tree.git/commit/9d193b758edaad192d05ebcb8dc4cb72711bf618
You were unfortunately a bit too late ;)
Regards,
Sylwester
prev parent reply other threads:[~2013-01-01 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 10:20 [PATCH 1/2] [media] s5p-jpeg: Use spinlock_t instead of 'struct spinlock' Sachin Kamat
2012-12-28 10:20 ` [PATCH 2/2] [media] s5p-fimc: " Sachin Kamat
2013-01-01 18:21 ` Sylwester Nawrocki [this message]
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=50E32940.80903@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=andrzej.p@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=patches@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=sachin.kamat@linaro.org \
/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).