From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: davem@davemloft.net, jeff@garzik.org
Subject: wireless administrivia (12 June 2007)
Date: Tue, 12 Jun 2007 22:57:50 -0400 [thread overview]
Message-ID: <20070613025750.GE4187@tuxdriver.com> (raw)
Just a quick memorandum...
I will be on vacation next week. My availability will be limited
starting Saturday (16 June) and stretching through the following
weekend. I will have some electronic accessibility and intend to
check-in at least once a day. However, I also intend to enjoy the
company of friends, my spouse, and my numerous (legitimate) offspring
as well as some tinkering with my own projects. :-)
Shortly after my vacation I will be off to sunny Canada for OLS2007.
I hope to see some of you there. I'm a bit portly, with short brown
(turning gray) hair and I'll probably have a tag with my name on
it -- men of Canada lock up your daughters! :-) Well if you see me,
feel free to say hello! Fedora users are especially welcome... :-)
So anyway, if you have any patches that need to get in (especially
for 2.6.22) then you should send them ASAP. I expect that I can
handle any truly "hot" emergency patches that might come-in during
the next two weeks, but anything less important (or more complicated)
than that will likely be delayed.
Also, if you have anything you are holding for the 2.6.23 merge window
then go ahead and post that as well. It would be best to give me,
Jeff, and Dave as much time to review things as possible. Drivers
currently sitting in wireless-dev would be good candidates for posting,
provided that they meet style and maintainability requirements, etc.
The above leads to something I mentioned in another thread. I would
like to reduce the delta between wireless-dev and upstream as much
as possible and as soon as possible. Pursuant to that, I would like
to set a goal for the group:
I would like to see anything which is currently sitting in
wireless-dev be ready for an upstream merge by the time the
2.6.24 (yes, 24) merge window opens.
The above is a "soft" goal -- I will almost certainly not be kicking
things out of wireless-dev simply for failing to meet it. Still, I
think this is a worthy goal and is doable for many parts of the tree.
I appreciate the effort that I expect will be exerted in order to
meet it.
Well, thanks for your attention...feel free to ask questions...
John
--
John W. Linville
linville@tuxdriver.com
next reply other threads:[~2007-06-13 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 2:57 John W. Linville [this message]
2007-07-03 18:52 ` wireless administrivia (12 June 2007) John W. Linville
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=20070613025750.GE4187@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.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).