From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org
Subject: Re: [PATCH] SPI/Pl022: Include types.h to remove compilation warnings
Date: Sat, 24 Mar 2012 16:55:15 +0000 [thread overview]
Message-ID: <20120324165515.E6D943E09BC@localhost> (raw)
In-Reply-To: <CACRpkdZV=NEbokQ4YGB=ueN0HkuqXZxqykodGC2MQ_KvBaaGKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 23 Mar 2012 10:48:57 +0100, Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
> On Fri, Mar 23, 2012 at 8:35 AM, Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org> wrote:
>
> > linux/pl022.h uses definitions like, u8, u16, etc, which have dependency of
> > types.h file, which isn't included in it. So, we get compilation warnings.
> >
> > This patch includes types.h there to fix these warnings.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
>
> Looks reasonable!
> Acked-by: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Applied, thanks.
g.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
prev parent reply other threads:[~2012-03-24 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 7:35 [PATCH] SPI/Pl022: Include types.h to remove compilation warnings Viresh Kumar
[not found] ` <2561efbfb6e8cf1c127dec7eca01bc69948bb94d.1332487932.git.viresh.kumar-qxv4g6HH51o@public.gmane.org>
2012-03-23 9:48 ` Linus Walleij
[not found] ` <CACRpkdZV=NEbokQ4YGB=ueN0HkuqXZxqykodGC2MQ_KvBaaGKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-24 16:55 ` Grant Likely [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=20120324165515.E6D943E09BC@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=viresh.kumar-qxv4g6HH51o@public.gmane.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.