From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Ohad Ben-Cohen <ohad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] wl12xx: fix non-wl12xx build scenarios
Date: Tue, 28 Sep 2010 21:09:43 +0300 [thread overview]
Message-ID: <1285697383.4728.10.camel@powerslave> (raw)
In-Reply-To: <1285692853-28248-1-git-send-email-ohad@wizery.com>
On Tue, 2010-09-28 at 18:54 +0200, ext Ohad Ben-Cohen wrote:
> After a linux-next discussion with John, I realized that building
> configs like:
This kind of comment in the commit log looks a bit odd. It should be a
bit more technical and direct to the point (ie. real life shouldn't be
included here ;)
If you want to include this kind of comments, you can use a cover-letter
or you can put the comments after the --- that comes after the
signed-off-by tag. Those comments won't be included in the git log.
> CONFIG_MACH_OMAP_ZOOM3=y
> CONFIG_WL12XX is not set
>
> will currently break.
>
> The general problem is building configs for wl1271-equipped boards
> without building the wl1271 driver itself.
>
> This patch fix this.
>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> Reported-by: John W. Linville <linville@tuxdriver.com>
> ---
Usually this order is the other way around. I think it makes sense to
keep the tags in chronological ordeer (ie. John reported first, then you
signed-off the patch that fixes it).
> include/linux/wl12xx.h | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/wl12xx.h b/include/linux/wl12xx.h
> index 95deae3..e1d758d 100644
> --- a/include/linux/wl12xx.h
> +++ b/include/linux/wl12xx.h
> @@ -32,7 +32,20 @@ struct wl12xx_platform_data {
> int board_ref_clock;
> };
>
> +#ifdef CONFIG_WL12XX_PLATFORM_DATA
> +
> int wl12xx_set_platform_data(const struct wl12xx_platform_data *data);
> +
> +#else /* !CONFIG_WL12XX_PLATFORM_DATA */
This is so small that I think the /* !CONFIG... */ is unnecessary.
> +
> +static inline int wl12xx_set_platform_data(const struct wl12xx_platform_data *
> + data)
It looks nicer if you break the line after static inline, like this:
static inline
int wl12xx_set_platform_data(const struct wl12xx platform_data *data)
> +{
> + return -ENOSYS;
> +}
> +
> +#endif /* !CONFIG_WL12XX_PLATFORM_DATA */
Comment unnecessary here too.
> const struct wl12xx_platform_data *wl12xx_get_platform_data(void);
>
> #endif
Otherwise it looks good and makes sense. :)
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-09-28 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 16:54 [PATCH] wl12xx: fix non-wl12xx build scenarios Ohad Ben-Cohen
2010-09-28 18:09 ` Luciano Coelho [this message]
2010-09-28 18:20 ` Ohad Ben-Cohen
2010-09-28 20:11 ` Luciano Coelho
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=1285697383.4728.10.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ohad@wizery.com \
/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).