From: David Miller <davem@davemloft.net>
To: lethal@linux-sh.org
Cc: nico@fluxnic.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: smc91x: Fix up type mismatch in smc_drv_resume().
Date: Fri, 11 Dec 2009 15:17:22 -0800 (PST) [thread overview]
Message-ID: <20091211.151722.243020071.davem@davemloft.net> (raw)
In-Reply-To: <20091211064226.GA7625@linux-sh.org>
From: Paul Mundt <lethal@linux-sh.org>
Date: Fri, 11 Dec 2009 15:42:27 +0900
> smc_drv_resume() takes a struct device, while smc_enable_device() takes a
> platform device. This fixes up the smc_enable_device() callsite with the
> proper pointer.
>
> It's not obvious when this change was introduced, as git history doesn't
> go back that far. Presumably the resume code has always been broken in
> this fashion.
>
> Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Applied.
prev parent reply other threads:[~2009-12-11 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 6:42 [PATCH] net: smc91x: Fix up type mismatch in smc_drv_resume() Paul Mundt
2009-12-11 23:17 ` David Miller [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=20091211.151722.243020071.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
/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).