From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Please pull 'upstream-davem' branch of wireless-2.6
Date: Wed, 3 Oct 2007 10:10:51 -0400 [thread overview]
Message-ID: <20071003141051.GA5790@tuxdriver.com> (raw)
In-Reply-To: <20071002.190156.41633562.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Tue, Oct 02, 2007 at 07:01:56PM -0700, David Miller wrote:
> From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> Date: Tue, 2 Oct 2007 21:25:52 -0400
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream-davem
>
> This doesn't pull cleanly.
>
> Probably you used a recently cloned Linus tree, pulled
> net-2.6.24 into that (and resolved the conflicts), and
> then put your patches in.
No, in fact I'm quite conscious of that. I follow a procedure
identical to what you outlined. I even leave my 'master-davem' branch
available as a reference, and create the initial 'upstream-davem'
branch as a checkout from it. :-)
As an experiment, I cloned your current tree (which has the patches
applied already, thanks!) and created a branch which backed-out the
patches from me you had already applied by hand. I then did a pull
from my tree, and the results were quite clean.
[linville]:> git checkout -b jwltest fc26d79bb258b5fdb3dee940bea12d6ef7c217c5
Switched to a new branch "jwltest"
[linville]:> git pull git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream-davem
remote: Generating pack...
remote: Done counting 257 objects.
remote: Result has 199 objects.
remote: Deltifying 199 objects...
remote: 100% (199/199) done
Indexing 199 objects...
remote: Total 199 (delta 150), reused 143 (delta 115)
100% (199/199) done
Resolving 150 deltas...
100% (150/150) done
32 objects were added to complete this thin pack.
Removed drivers/net/wireless/zd1211rw/zd_util.c
Removed drivers/net/wireless/zd1211rw/zd_util.h
Merge made by recursive.
Documentation/networking/mac80211-injection.txt | 32 ++-
drivers/net/wireless/adm8211.c | 8 +-
drivers/net/wireless/b43/Kconfig | 12 +
drivers/net/wireless/b43/Makefile | 5 +-
drivers/net/wireless/b43/b43.h | 11 +-
drivers/net/wireless/b43/leds.c | 399 ++++++++++-------------
drivers/net/wireless/b43/leds.h | 63 ++--
drivers/net/wireless/b43/main.c | 205 ++++--------
drivers/net/wireless/b43/phy.c | 13 +-
drivers/net/wireless/b43/phy.h | 2 +-
drivers/net/wireless/b43/rfkill.c | 184 +++++++++++
drivers/net/wireless/b43/rfkill.h | 58 ++++
drivers/net/wireless/hostap/hostap.h | 2 +-
drivers/net/wireless/hostap/hostap_hw.c | 2 +-
drivers/net/wireless/hostap/hostap_main.c | 19 +-
drivers/net/wireless/iwlwifi/iwl3945-base.c | 4 -
drivers/net/wireless/iwlwifi/iwl4965-base.c | 4 -
drivers/net/wireless/p54common.c | 4 +-
drivers/net/wireless/p54pci.c | 4 +-
drivers/net/wireless/rt2x00/rt2x00.h | 2 +-
drivers/net/wireless/zd1211rw/Makefile | 2 +-
drivers/net/wireless/zd1211rw/zd_chip.c | 1 -
drivers/net/wireless/zd1211rw/zd_mac.c | 4 +-
drivers/net/wireless/zd1211rw/zd_usb.c | 1 -
drivers/net/wireless/zd1211rw/zd_util.c | 82 -----
drivers/net/wireless/zd1211rw/zd_util.h | 29 --
include/linux/rfkill.h | 24 ++
include/net/mac80211.h | 46 +++-
net/mac80211/cfg.c | 75 ++++-
net/mac80211/ieee80211.c | 189 +-----------
net/mac80211/ieee80211_i.h | 17 +-
net/mac80211/ieee80211_iface.c | 68 +----
net/mac80211/ieee80211_ioctl.c | 31 +-
net/mac80211/ieee80211_led.c | 67 +++-
net/mac80211/ieee80211_led.h | 6 +
net/mac80211/ieee80211_rate.c | 3 +-
net/mac80211/ieee80211_rate.h | 2 -
net/mac80211/ieee80211_sta.c | 7 +-
net/mac80211/key.c | 1 -
net/mac80211/rx.c | 122 +++-----
net/mac80211/sta_info.c | 13 +-
net/mac80211/tx.c | 211 ++++++------
net/mac80211/wme.c | 10 +-
net/rfkill/Kconfig | 7 +
net/rfkill/rfkill.c | 49 +++-
45 files changed, 1022 insertions(+), 1078 deletions(-)
create mode 100644 drivers/net/wireless/b43/rfkill.c
create mode 100644 drivers/net/wireless/b43/rfkill.h
delete mode 100644 drivers/net/wireless/zd1211rw/zd_util.c
delete mode 100644 drivers/net/wireless/zd1211rw/zd_util.h
So I'm not sure what happened for you. But I think it must have been
some other anomaly.
Anyway, I'm sorry it wasn't as smooth as usual. Thanks for the manual
patch work!
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2007-10-03 14:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 1:25 Please pull 'upstream-davem' branch of wireless-2.6 John W. Linville
[not found] ` <20071003012552.GE29361-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-10-03 1:45 ` John W. Linville
2007-10-03 2:01 ` David Miller
[not found] ` <20071002.190156.41633562.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-10-03 14:10 ` John W. Linville [this message]
[not found] ` <20071003141051.GA5790-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-10-03 21:52 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-01-08 19:29 John W. Linville
[not found] ` <20080108192914.GA3086-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-01-09 7:36 ` David Miller
2007-12-20 15:53 John W. Linville
2007-12-20 22:38 ` John W. Linville
[not found] ` <20071220223850.GL3139-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-12-21 4:04 ` David Miller
2007-12-17 20:55 John W. Linville
[not found] ` <20071217205540.GH3121-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-12-18 6:57 ` David Miller
2007-12-01 2:23 John W. Linville
[not found] ` <20071201022306.GA28032-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-12-01 13:54 ` Herbert Xu
2007-11-20 22:11 John W. Linville
[not found] ` <20071120221135.GI16090-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-11-21 1:27 ` David Miller
2007-11-07 3:08 John W. Linville
2007-11-20 5:24 ` David Miller
2007-10-10 0:21 John W. Linville
[not found] ` <20071010002145.GD3175-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-10-10 1:13 ` David Miller
2007-09-15 13:20 John W. Linville
2007-08-15 0:32 Please pull 'fixes-davem' " John W. Linville
[not found] ` <20070815003234.GI7198-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-08-15 0:34 ` Please pull 'upstream-davem' " John W. Linville
[not found] ` <20070815003410.GJ7198-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-08-15 23:09 ` David Miller
2007-08-19 23:32 ` David Miller
2007-08-06 20:13 Please pull 'fixes-davem' " John W. Linville
2007-08-06 21:01 ` Please pull 'upstream-davem' " John W. Linville
2007-08-09 9:00 ` David Miller
2007-07-18 2:16 John W. Linville
2007-07-18 3:17 ` David Miller
[not found] ` <20070717.201716.112622844.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-07-18 15:34 ` John W. Linville
[not found] ` <20070718153449.GA6625-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-07-18 22:32 ` David Miller
2007-07-19 0:45 ` John W. Linville
2007-07-19 1:21 ` David Miller
2007-07-12 20:41 John W. Linville
[not found] ` <20070712204137.GB14486-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-07-15 1:59 ` David Miller
[not found] ` <20070714.185935.18577806.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-07-15 3:41 ` David Miller
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=20071003141051.GA5790@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@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 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).