linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Andy Green <andy@warmcat.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	"John W. Linville" <linville@tuxdriver.com>,
	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:37:24 +0200	[thread overview]
Message-ID: <1184917044.23536.4.camel@johannes.berg> (raw)
In-Reply-To: <46A050B4.3060500@warmcat.com>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

On Fri, 2007-07-20 at 07:05 +0100, Andy Green wrote:

> After seeing patch tracking issues on arm-linux mailing list as well,
> those not involving me, I started making a PHP project called
> "patchfillet" for the purpose of extracting patches from a mailing list
> and trying to track the patch lifecycle in an automated way driven by
> the contents of the threads (eg, keywords like adding Acked-by: <blah>
> in a reply) and maybe one day by looking at an upstream git repo commits
> (I found that the Index: line in git-committed patches can change
> destroying what would otherwise be a hash match).

Sounds like `patchwork'.

> 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 :)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2007-07-20  7:37 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 [this message]
2007-07-20 13:31           ` John W. Linville
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=1184917044.23536.4.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=andy@warmcat.com \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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).