linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] p54usb: fix conflict with recent usb changes
Date: Fri, 16 Jan 2009 16:13:52 -0500	[thread overview]
Message-ID: <20090116211351.GA15245@tuxdriver.com> (raw)
In-Reply-To: <200901162024.31636.chunkeey@web.de>

On Fri, Jan 16, 2009 at 08:24:31PM +0100, Christian Lamparter wrote:
> A recent change in the usb core "USB: change interface to usb_lock_device_for_reset()" 
> conflicts with "p54usb: utilize usb_reset_device for 3887".
> 
> Sadly, we have to call usb_reset_device before we can upload the firmware on 3887.
> Unless someone figures out how to reliably stop the 3887 so the hardware is still usable
> next time we want to start it.
> 
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> ---
> John,
> 
> I guess this patch should be in the next wireless-2.6 pull.
> And it would be nice, if you can put "[PATCH] p54: fix p54_set_key's return code" in there too. 

The other patch seems fine, but this one doesn't apply to wireless-2.6
-- p54u_device_reset_3887 doesn't seem to exist there?

I'll apply this in wireless-testing and eventually to wireless-next-2.6,
unless you send me an alternative patch based on wireless-2.6?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-01-16 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 19:24 [PATCH] p54usb: fix conflict with recent usb changes Christian Lamparter
2009-01-16 21:13 ` John W. Linville [this message]
2009-01-16 22:06   ` Christian Lamparter

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=20090116211351.GA15245@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@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 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).