From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Andy Green <andy@warmcat.com>, Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org,
Larry Finger <larry.finger@lwfinger.net>
Subject: Re: [PATCH 2/2] bcm43xx-mac80211: Fix reported rx frequency and channel
Date: Fri, 20 Jul 2007 09:31:34 -0400 [thread overview]
Message-ID: <20070720133134.GB7428@tuxdriver.com> (raw)
In-Reply-To: <1184917044.23536.4.camel@johannes.berg>
On Fri, Jul 20, 2007 at 09:37:24AM +0200, Johannes Berg wrote:
> On Fri, 2007-07-20 at 07:05 +0100, Andy Green wrote:
> > I must say an explicit ACK or NAK for patches is a great idea.
>
> I'd also appreciate explicit davem-style "thanks I merged this" but hey,
> I get by checking the various git trees all the time :)
Yes, I could do better. Still, checking the "Please pull..." message
short logs might be more time efficient.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-20 14:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 10:38 [PATCH 0/2] Small driver fixes andy
2007-06-11 10:38 ` [PATCH 1/2] zd1211rw-mac80211: return hardware specific tx rate code for rx status andy
2007-07-19 19:10 ` John W. Linville
2007-07-19 21:19 ` Ulrich Kunitz
2007-06-11 10:38 ` [PATCH 2/2] bcm43xx-mac80211: Fix reported rx frequency and channel andy
2007-06-11 11:26 ` Johannes Berg
2007-06-11 11:45 ` Johannes Berg
2007-07-19 19:10 ` John W. Linville
2007-07-19 19:39 ` Michael Buesch
2007-07-20 6:05 ` Andy Green
2007-07-20 7:37 ` Johannes Berg
2007-07-20 13:31 ` John W. Linville [this message]
2007-07-20 14:36 ` Larry Finger
2007-07-20 14:47 ` Andy Green
2007-07-20 16:58 ` Larry Finger
2007-07-20 17:36 ` Michael Buesch
2007-07-20 17:48 ` Andy Green
2007-07-20 17:50 ` Michael Buesch
2007-07-20 20:40 ` Johannes Berg
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=20070720133134.GB7428@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=andy@warmcat.com \
--cc=johannes@sipsolutions.net \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.