From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: reinette.chatre@intel.com
Subject: wireless-next-2.6 rebased from commit bc53e5129ce879ba024b7d21981871ea63a37b42
Date: Wed, 7 Apr 2010 14:55:09 -0400 [thread overview]
Message-ID: <20100407185509.GA3058@tuxdriver.com> (raw)
I accidentally pushed some junk to wireless-next-2.6 yesterday.
It didn't get pulled into wireless-testing and it wasn't sent to Dave,
but just in case anyone pulled wireless-next-2.6 in the past day or
so you should be aware of a coming "forced" update.
Sorry for the inconvenience!
John
P.S. I just removed a revert an the original patch it was reverting --
the diff should be zero.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
reply other threads:[~2010-04-07 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100407185509.GA3058@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/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.