From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] sparse warnings
Date: Fri, 11 Apr 2008 12:05:14 -0700 [thread overview]
Message-ID: <20080411190513.GE7717@atomide.com> (raw)
In-Reply-To: <1207911557-9392-1-git-send-email-felipe.balbi@nokia.com>
* Felipe Balbi <felipe.balbi@nokia.com> [080411 04:00]:
> The following two patches get rids of most sparse warnings
> in musb and twl4030 drivers.
>
> Some of them still there because it didn't make sense fixing.
> The most notable case is the preprocessor macros in the pr_info()
> at musb_init() and lack of use of twl4030*gpio*() at twl4030-gpio.c.
Pushing these too.
Tony
> Felipe Balbi (2):
> USB: MUSB: sparse fixes to musb_hdrc driver
> I2C: TWL4030: sparse fixes for twl4030 driver
>
> drivers/i2c/chips/twl4030-core.c | 2 +-
> drivers/i2c/chips/twl4030-gpio.c | 53 ++++++++++++++++------------------
> drivers/i2c/chips/twl4030-poweroff.c | 2 +-
> drivers/usb/musb/musb_host.c | 6 ++--
> drivers/usb/musb/musbhsdma.c | 6 ++--
> 5 files changed, 33 insertions(+), 36 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-04-11 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 10:59 [PATCH 0/2] sparse warnings Felipe Balbi
2008-04-11 10:59 ` [PATCH 1/2] USB: MUSB: sparse fixes to musb_hdrc driver Felipe Balbi
2008-04-11 10:59 ` [PATCH 2/2] I2C: TWL4030: sparse fixes for twl4030 driver Felipe Balbi
2008-04-11 19:05 ` Tony Lindgren [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=20080411190513.GE7717@atomide.com \
--to=tony@atomide.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@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