From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: jeff@garzik.org, netdev@vger.kernel.org, akpm@osdl.org,
torvalds@osdl.org
Subject: Re: Please pull upstream-fixes branch of wireless-2.6
Date: Thu, 20 Apr 2006 10:51:03 +0200 [thread overview]
Message-ID: <200604201051.03881.mb@bu3sch.de> (raw)
In-Reply-To: <20060420011232.GA9268@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
On Thursday 20 April 2006 03:12, John W. Linville wrote:
> bcm43xx: fix dyn tssi2dbm memleak
> bcm43xx: fix pctl slowclock limit calculation
> bcm43xx: sysfs code cleanup
These are already in -mm and on their way into linus's tree.
Is it possible to cause problems?
If not, fine. If yes, we need some clearly defined rules where
to put patches and a clearly defined statement of how often
patches are pushed upstream.
--
Greetings Michael.
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-20 8:47 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 1:12 Please pull upstream-fixes branch of wireless-2.6 John W. Linville
2006-04-20 8:51 ` Michael Buesch [this message]
2006-04-20 8:57 ` Andrew Morton
2006-04-20 9:12 ` Michael Buesch
2006-04-20 12:53 ` John W. Linville
2006-04-20 19:58 ` Andrew Morton
2006-04-20 22:28 ` Linus Torvalds
2006-04-20 9:00 ` Jeff Garzik
2006-04-20 21:36 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 19:40 Please pull 'upstream-fixes' " John W. Linville
2006-04-26 10:17 ` Jeff Garzik
2006-05-06 1:06 Please pull upstream-fixes " John W. Linville
2006-05-06 3:08 ` Andrew Morton
2006-05-06 3:20 ` Linus Torvalds
2006-05-06 4:12 ` Stephen Hemminger
2006-05-06 13:45 ` John W. Linville
2006-05-17 19:34 Please pull 'upstream-fixes' " John W. Linville
2006-05-22 19:18 John W. Linville
2006-05-24 4:26 ` Jeff Garzik
2006-05-24 8:52 ` Andrew Morton
2006-05-26 20:37 John W. Linville
2006-05-27 1:26 ` Jeff Garzik
2006-06-05 21:53 John W. Linville
2006-06-08 19:46 ` Jeff Garzik
2006-07-10 21:29 John W. Linville
2006-07-28 0:22 John W. Linville
2006-07-29 4:32 ` Jeff Garzik
2006-08-02 21:56 John W. Linville
2006-08-03 21:19 ` Jeff Garzik
2006-08-04 20:58 John W. Linville
2006-08-09 3:48 ` Jeff Garzik
2006-08-23 18:46 John W. Linville
2006-08-24 4:41 ` Jeff Garzik
2006-09-11 23:58 John W. Linville
2006-09-12 15:42 ` Jeff Garzik
2006-10-17 21:34 John W. Linville
2006-10-21 18:22 ` Jeff Garzik
2006-11-08 4:58 John W. Linville
2006-11-10 16:11 ` Jeff Garzik
2006-11-15 1:29 John W. Linville
2006-11-28 19:14 ` John W. Linville
2006-12-21 3:03 John W. Linville
2006-12-26 21:39 ` Jeff Garzik
2007-01-03 2:41 John W. Linville
2007-01-18 15:48 John W. Linville
2007-01-18 16:46 ` Jeff Garzik
2007-02-02 21:27 Please pull "upstream-fixes" " John W. Linville
[not found] ` <20070202212747.GC9382-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-02-07 0:06 ` Jeff Garzik
2007-05-22 15:17 Please pull 'upstream-fixes' " John W. Linville
2007-05-29 18:30 John W. Linville
[not found] ` <20070529183037.GB3496-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-05-30 13:46 ` Jeff Garzik
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=200604201051.03881.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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 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).