From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] wbsd pnp suspend
Date: Tue, 08 Nov 2005 07:57:01 +0100 [thread overview]
Message-ID: <43704C3D.30602@drzeus.cx> (raw)
In-Reply-To: <20051107225019.7cd01a77.akpm@osdl.org>
Andrew Morton wrote:
> Pierre Ossman <drzeus@drzeus.cx> wrote:
>> Allow the wbsd driver to use the new suspend/resume functions added to
>> the PnP layer.
>>
>
> Doesn't Russell handle mmc stuff?
>
Yup. But this needs the PnP suspend stuff in your patch set.
>> -static int wbsd_suspend(struct device *dev, pm_message_t state)
>> +static int wbsd_suspend(struct wbsd_host *host, pm_message_t state)
>> +{
>> + BUG_ON(host == NULL);
>> +
>> + return mmc_suspend_host(host->mmc, state);
>> +}
>
> There's not much point in this BUG_ON. If host==0 then we'll get a
> perfectly good oops in the next statement - it's just as informative.
>
I suppose. I just have a tendency to scatter assertions all over the
place. :)
>> + if (host->config != 0)
>> + {
>> + if (!wbsd_chip_validate(host))
>> + {
>
> Like:
>
> if (host->config != 0) {
> if (!wbsd_chip_validate(host)) {
>
> please.
>
We had this discussion the last patch for this driver. It's horribly
wrong when it comes to coding style so keeping patches in the same style
as the rest of the driver is the lesser evil (IMHO).
Rgds
Pierre
next prev parent reply other threads:[~2005-11-08 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 6:41 [PATCH] [MMC] wbsd pnp suspend Pierre Ossman
2005-11-08 6:50 ` Andrew Morton
2005-11-08 6:57 ` Pierre Ossman [this message]
2005-11-08 7:06 ` Dmitry Torokhov
2005-11-08 8:45 ` Pierre Ossman
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 23:02 Pierre Ossman
2006-01-08 14:23 ` Russell King
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=43704C3D.30602@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=akpm@osdl.org \
--cc=linux-kernel@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.