From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-sh@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: sh-sci: Fix warnings due to improper casts and printk formats
Date: Fri, 29 Nov 2013 00:12:12 +0000 [thread overview]
Message-ID: <20131129001208.GA6462@verge.net.au> (raw)
In-Reply-To: <1772107.qNxlNP4NDS@avalon>
On Thu, Nov 28, 2013 at 03:00:35PM +0100, Laurent Pinchart wrote:
> Hi Simon,
>
> On Thursday 28 November 2013 16:27:31 Simon Horman wrote:
> > On Wed, Nov 27, 2013 at 11:10:37AM +0100, Laurent Pinchart wrote:
> > > Use the %zu printk specifier to print size_t variables, and cast
> > > pointers to uintptr_t instead of unsigned int where applicable. This
> > > fixes warnings on platforms where pointers and/or dma_addr_t have a
> > > different size than int.
> > >
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: linux-serial@vger.kernel.org
> > > Signed-off-by: Laurent Pinchart
> > > <laurent.pinchart+renesas@ideasonboard.com>
> >
> > Acked-by: Simon Horman <horms+renesas@verge.net.au>
> >
> > Laurent, I am assuming that you would like Greg to take this one.
>
> Actually, as we have quite a few pending sh-sci patches interleaved with
> arch/arm patches, it would be easier if all sh-sci patches went through your
> tree for this kernel version. That's if Greg agrees of course.
Thanks, that is fine by me so long as its fine by Greg and I get
an Ack from him for each of the sh-sci that go into my tree.
next prev parent reply other threads:[~2013-11-29 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:10 [PATCH v2] serial: sh-sci: Fix warnings due to improper casts and printk formats Laurent Pinchart
2013-11-28 7:27 ` Simon Horman
2013-11-28 14:00 ` Laurent Pinchart
2013-11-29 0:12 ` Simon Horman [this message]
2013-12-03 18:45 ` Greg Kroah-Hartman
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=20131129001208.GA6462@verge.net.au \
--to=horms@verge.net.au \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-serial@vger.kernel.org \
--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 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).