From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>
Subject: Re: [PATCH 5/5 V2] b43: N-PHY: silence warnings, add missing call
Date: Tue, 19 Jan 2010 16:55:28 -0500 [thread overview]
Message-ID: <20100119215528.GB3078@tuxdriver.com> (raw)
In-Reply-To: <op.u6o9unx49lhzdc@linux-g0th.site>
On Mon, Jan 18, 2010 at 12:21:49AM +0100, Rafał Miłecki wrote:
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> ---
> New patch I didn't include earlier.
Rafał,
I just applied this 5-patch series and the preceding 7-patch series,
and I had to fixup every single one manually due to the apparently
busted mailer you are using.
User-Agent: Opera Mail/10.10 (Linux)
The only reason I went to this trouble is because a) I want the
N-phy stuff and b) you sent small, manageable patches. But don't
misunderstand -- I have no intention of continuing to fix these
manually.
Learn to use "git send-email" or find some other mailer to send
your patches -- I recommend Mutt. In any case, do not expect your
patches to get merged unless in the future unless you can rectify
this situation at your end. I just don't have the bandwidth for
dealing with crap like this.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-01-19 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 23:21 [PATCH 5/5 V2] b43: N-PHY: silence warnings, add missing call Rafał Miłecki
2010-01-19 21:55 ` John W. Linville [this message]
2010-01-19 22:32 ` Luis R. Rodriguez
2010-01-19 22:55 ` Rafał Miłecki
2010-01-19 22:59 ` Rafał Miłecki
2010-01-20 10:52 ` Michael Buesch
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=20100119215528.GB3078@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).