netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: steve.glendinning@smsc.com
Cc: netdev@vger.kernel.org, ian.saturley@smsc.com, oliver@neukum.org
Subject: Re: [PATCH] smsc95xx: fix function prototype of async callback
Date: Sun, 25 Jan 2009 17:54:58 -0800 (PST)	[thread overview]
Message-ID: <20090125.175458.70126165.davem@davemloft.net> (raw)
In-Reply-To: <1232464140-27713-1-git-send-email-steve.glendinning@smsc.com>

From: Steve Glendinning <steve.glendinning@smsc.com>
Date: Tue, 20 Jan 2009 15:09:00 +0000

> smsc95xx_async_cmd_callback doesn't currently match usb_complete_t, so
> there's a cast to force the square peg into the round hole.  This patch
> fixes this properly.
> 
> Signed-off-by: Steve Glendinning <steve.glendinning@smsc.com>

Applied.

      reply	other threads:[~2009-01-26  1:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 15:09 [PATCH] smsc95xx: fix function prototype of async callback Steve Glendinning
2009-01-26  1:54 ` 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=20090125.175458.70126165.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ian.saturley@smsc.com \
    --cc=netdev@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=steve.glendinning@smsc.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).