From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Simon Horman <horms@verge.net.au>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-sh@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: rsnd: Fix warnings due to improper printk formats
Date: Wed, 14 May 2014 11:33:08 +0900 [thread overview]
Message-ID: <5372D5E4.9060300@renesas.com> (raw)
In-Reply-To: <20140513213935.GA6784@verge.net.au>
Hi
>>> Use the %pap printk specifier to print resource_size_t variables. This
>>> fixes warnings on platforms where resource_size_t has a different size
>>> than int.
>>>
>>> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>>> ---
>>
>> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Morimoto-san, should Mark Brown need to be CCed on a re-post
> in order for him to see this?
Ahh, I didn't notice that Mark wasn't CCed.
He never (?) accepts patch which doesn't have "To" him.
Please use this address,
broonie@kernel.org
WARNING: multiple messages have this Message-ID (diff)
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Simon Horman <horms@verge.net.au>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-sh@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: rsnd: Fix warnings due to improper printk formats
Date: Wed, 14 May 2014 02:33:08 +0000 [thread overview]
Message-ID: <5372D5E4.9060300@renesas.com> (raw)
In-Reply-To: <20140513213935.GA6784@verge.net.au>
Hi
>>> Use the %pap printk specifier to print resource_size_t variables. This
>>> fixes warnings on platforms where resource_size_t has a different size
>>> than int.
>>>
>>> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>>> ---
>>
>> Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Morimoto-san, should Mark Brown need to be CCed on a re-post
> in order for him to see this?
Ahh, I didn't notice that Mark wasn't CCed.
He never (?) accepts patch which doesn't have "To" him.
Please use this address,
broonie@kernel.org
next prev parent reply other threads:[~2014-05-14 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 23:10 [PATCH] ASoC: rsnd: Fix warnings due to improper printk formats Laurent Pinchart
2014-05-12 23:10 ` Laurent Pinchart
2014-05-12 23:53 ` Kuninori Morimoto
2014-05-12 23:53 ` Kuninori Morimoto
2014-05-13 21:39 ` Simon Horman
2014-05-13 21:39 ` Simon Horman
2014-05-14 2:33 ` Kuninori Morimoto [this message]
2014-05-14 2:33 ` Kuninori Morimoto
2014-05-15 10:14 ` [alsa-devel] " Mark Brown
2014-05-15 10:14 ` Mark Brown
2014-05-15 12:10 ` Laurent Pinchart
2014-05-15 12:10 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2014-03-04 18:10 Laurent Pinchart
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=5372D5E4.9060300@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@vger.kernel.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 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.