All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Broadcom Linux
	<bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org>,
	Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>,
	Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
	Larry Finger
	<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Subject: Re: [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx
Date: Sat, 09 Sep 2006 15:42:37 -0400	[thread overview]
Message-ID: <4503192D.4010509@gentoo.org> (raw)
In-Reply-To: <4502E62B.5060601-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>

John,

Larry Finger wrote:
> I would like to get a listing of patches for bcm43xx-softmac that are 
> queued but not yet applied, and the order in which they will be applied. 
> I want to make sure nothing has fallen through the cracks, and that the 
> patches will apply cleanly.

I know you have various other commitments but I would also find it 
beneficial if you could reduce the amount of time it takes between the 
patch arriving in your inbox and the commit appearing in 
wireless-2.6.git on kernel.org.

I'm currently waiting on the last few ZD1211 patches to appear in the 
git tree before sending the next few, since otherwise I have to 
backtrack and find out which patches I have already sent before 
producing the next batch.

I'm probably just being lazy -- the current scheme is workable, it is 
just a simple matter of convenience to have the patches appearing in git 
relatively quickly (even if there is still a delay before they head 
Jeffwards).

Thanks!
Daniel

  parent reply	other threads:[~2006-09-09 19:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09  1:47 [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx Larry Finger
     [not found] ` <45021D4A.6040805-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 15:23   ` John W. Linville
2006-09-09 16:04     ` Larry Finger
     [not found]       ` <4502E62B.5060601-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 19:42         ` Daniel Drake [this message]
2006-09-11 19:28         ` John W. Linville
2006-09-11 19:59           ` Larry Finger
     [not found]             ` <4505C005.2070302-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-11 20:35               ` John W. Linville
2006-09-11 22:04                 ` Jeff Garzik
2006-09-14  8:25                   ` Jarek Poplawski
2006-09-14  8:29                     ` Jarek Poplawski
2006-10-05 20:52                       ` Randy Dunlap
2006-10-06  5:57                         ` Jarek Poplawski
2006-10-06  6:19                           ` Jarek Poplawski
2006-10-06  6:57                           ` Jarek Poplawski

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=4503192D.4010509@gentoo.org \
    --to=dsd-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
    --cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org \
    /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.