From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] net/fec: clean suspend/resume
Date: Fri, 25 Jun 2010 21:36:17 -0700 (PDT) [thread overview]
Message-ID: <20100625.213617.235709938.davem@davemloft.net> (raw)
In-Reply-To: <1276853351-20790-1-git-send-email-eric@eukrea.com>
From: Eric B?nard <eric@eukrea.com>
Date: Fri, 18 Jun 2010 11:29:10 +0200
> Commit 59d4289b83b11379d867e2f7146904b19cc96404 converted fec to dev_pm_ops but
> didn't update the suspend/resume functions thus leading to the following warning :
> "initialization from incompatible pointer type" when CONFIG_PM is set.
>
> This patch also fixe a few indentation and style around CONFIG_PM area.
>
> Signed-off-by: Eric B?nard <eric@eukrea.com>
Applied.
next prev parent reply other threads:[~2010-06-26 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 9:29 [PATCH 1/2] net/fec: clean suspend/resume Eric Bénard
2010-06-25 5:05 ` David Miller
2010-06-25 6:54 ` Eric Bénard
2010-06-26 4:36 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-18 14:19 Eric Bénard
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=20100625.213617.235709938.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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).