From: Christian Lamparter <chunkeey@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54: parse output power table
Date: Mon, 6 Aug 2012 21:27:12 +0200 [thread overview]
Message-ID: <201208062127.12933.chunkeey@googlemail.com> (raw)
In-Reply-To: <20120806190317.GB26210@tuxdriver.com>
On Monday, August 06, 2012 09:03:17 PM John W. Linville wrote:
> patching file drivers/net/wireless/p54/eeprom.c
> Hunk #1 succeeded at 77 with fuzz 2 (offset 1 line).
> Hunk #2 succeeded at 175 (offset 1 line).
> Hunk #3 FAILED at 192.
> Hunk #4 succeeded at 233 (offset 2 lines).
> Hunk #5 FAILED at 244.
> Hunk #6 succeeded at 321 (offset 3 lines).
> Hunk #7 succeeded at 847 (offset 3 lines).
hmm, it applies cleanly here.
Do you have another patch in your pipeline?
(If it's the tpc patch that is causing the
rejects, then can you please drop it, as it
depends on the tpc algorithm which isn't
in place yet)
Regards,
Chr
prev parent reply other threads:[~2012-08-06 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 0:57 [PATCH] p54: parse output power table Christian Lamparter
2012-08-06 19:03 ` John W. Linville
2012-08-06 19:27 ` Christian Lamparter [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=201208062127.12933.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--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