From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [patch 0/7] SSB: New patch series for merge
Date: Tue, 14 Aug 2007 17:18:35 -0500 [thread overview]
Message-ID: <46C22A3B.1090802@lwfinger.net> (raw)
In-Reply-To: <200708141938.33952.mb@bu3sch.de>
Michael Buesch wrote:
> On Tuesday 14 August 2007 19:34:08 Larry Finger wrote:
>> Michael Buesch wrote:
>>> Hi John,
>>>
>>> This patch series catches SSB up to my
>>> current wireless-development patchset.
>>>
>>> Please merge this into wireless-dev ssb branch.
>> I had a problem with #7. My copy of John's tree still has EXPERIMENTAL for ssb. Yours does not.
>
> Are you sure you have latest wireless-dev? It has
> been rebased again.
>
Indeed, that was the problem. Once I got John's email and learned how to handle the new rebase, you
patch applied just fine.
Larry
prev parent reply other threads:[~2007-08-14 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 17:00 [patch 0/7] SSB: New patch series for merge Michael Buesch
2007-08-14 17:34 ` Larry Finger
2007-08-14 17:38 ` Michael Buesch
2007-08-14 22:18 ` Larry Finger [this message]
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=46C22A3B.1090802@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).