From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: libertas-dev@lists.infradead.org, Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH, take 2] libertas: unify various CF-related defines
Date: Mon, 2 Jun 2008 08:41:21 +0200 [thread overview]
Message-ID: <200806020841.21481.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20080530154113.GB9490@tuxdriver.com>
On Friday 30 May 2008 17:41:13 John W. Linville wrote:
> On Mon, May 26, 2008 at 12:50:50PM +0200, Holger Schurig wrote:
> > Signed-off-by: Holger Schurig <hs4233@mail.mn-solutions.de>
>
> git says:
>
> Applying libertas: don't spin_unlock_irq() twice
> Applying libertas: speeds up downloading of CF firmware
> Applying libertas: use lbs_pr_XX instead of printk
> Applying libertas: before sleeping, check for a command result
> Applying libertas: unify various CF-related defines
> error: patch failed: drivers/net/wireless/libertas/if_cs.c:221
> error: drivers/net/wireless/libertas/if_cs.c: patch does not
> apply
It should applied after "Re: [PATCH, take 3] libertas: fix
compact flash interrupt handling".
next prev parent reply other threads:[~2008-06-02 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 10:50 [PATCH, take 2] libertas: unify various CF-related defines Holger Schurig
2008-05-27 20:14 ` Dan Williams
2008-05-30 15:41 ` John W. Linville
2008-06-02 6:41 ` Holger Schurig [this message]
2008-06-02 7:25 ` [PATCH, RESEND] " Holger Schurig
2008-06-03 0:57 ` John W. Linville
2008-06-03 8:18 ` Holger Schurig
2008-06-03 14:03 ` John W. Linville
2008-06-03 14:14 ` Dan Williams
2008-06-03 14:58 ` [PATCH] libertas: fixup if_usb_reset_olpc_card warnings for OLPC John W. Linville
2008-06-03 14:59 ` [PATCH, RESEND] libertas: unify various CF-related defines John W. Linville
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=200806020841.21481.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dcbw@redhat.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).