netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: netdev@vger.kernel.org
Subject: wireless-2.6 now has a 'pending' branch (was Re: Please pull 'upstream' branch of wireless-2.6.git)
Date: Mon, 25 Sep 2006 17:55:36 -0400	[thread overview]
Message-ID: <20060925215535.GH16949@tuxdriver.com> (raw)
In-Reply-To: <20060925215037.GG16949@tuxdriver.com>

On Mon, Sep 25, 2006 at 05:50:43PM -0400, John W. Linville wrote:
> The following changes since commit 7c250413e5b7c3dfae89354725b70c76d7621395:
>   Al Viro:
>         pata_pdc2027x iomem annotations
> 
> are found in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream

It's been a little while, and for that I apologize.  Work, kids, elderly
relatives, blah, blah, blah... :-(

Anyway, this covers _almost_ everything I've got in my queue for pushing
upstream.  The exceptions are a couple of patches posted very recently
which I'd like to give a chance to simmer first.  That gives people a
little more time to review them rather than asking me to revert them
later... :-)

Anyway, I know have a "pending" branch.  Patches on this branch are
really only there for three reasons:

	-- to let the author know I got the patch;

	-- to let me know that the patch applies to the tree; and,

	-- to enhance a patch's exposure for review.

I do not intend to add my "Signed-off-by:" to patches on the pending
branch.  This is intended to further signify (albeit subtley) that
they are not yet queued for upstream.  This also implies that I won't
be pulling from that branch, so you shouldn't be pulling from there
into your own trees either (except for the purpose of reviewing the
patches, of course).  I probably won't usually announce new patches
in the pending branch, so feel free to check it periodically.

For now, the pending branch is just a trial intended to add more
visibility to the process.  Feel free to propose changes to the
pending process if it does not seem to be effective.  YMMV, objects
in mirror may be closer than they appear, you are not expected to
understand this, etc... :-)

John

P.S.  Individual patches are available here (w/o using git):

	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/pending

---

The following changes since commit a67ab2bde752b26be75d4b68ecead9a14692eac5:
  Larry Finger:
        bcm43xx: fix netdev watchdog timeouts

are found in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git pending

Daniel Drake:
      ieee80211: Move IV/ICV stripping into ieee80211_rx

Larry Finger:
      ieee80211: quiet TKIP and CCMP replay messages for identical TSCs

 drivers/net/wireless/bcm43xx/bcm43xx_main.c |    3 +
 drivers/net/wireless/bcm43xx/bcm43xx_xmit.c |   19 ---------
 drivers/net/wireless/ipw2200.c              |   48 +----------------------
 include/net/ieee80211.h                     |    4 ++
 net/ieee80211/ieee80211_crypt_ccmp.c        |    2 -
 net/ieee80211/ieee80211_crypt_tkip.c        |    2 -
 net/ieee80211/ieee80211_rx.c                |   56 ++++++++++++++++++++++++---
 7 files changed, 61 insertions(+), 73 deletions(-)
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2006-09-25 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 21:50 Please pull 'upstream' branch of wireless-2.6.git John W. Linville
2006-09-25 21:55 ` John W. Linville [this message]
2006-09-26  0:09 ` 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=20060925215535.GH16949@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=netdev@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).