From: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Please pull 'fixes-jgarzik' branch of wireless-2.6 (3rd time is the charm?)
Date: Thu, 8 Nov 2007 12:53:28 -0500 [thread overview]
Message-ID: <20071108175328.GA3491@havoc.gtf.org> (raw)
In-Reply-To: <20071108142626.GH11957-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
On Thu, Nov 08, 2007 at 09:26:26AM -0500, John W. Linville wrote:
> Jeff,
>
> OK, I think things are settled now. I apologize for the confusion.
>
> These are fixes intended for 2.6.24. Please note that three of the
> patches from Michael Buesch in the list below were already sent to
> you directed for 2.6.25. Upon further review, I think they belong in
> 2.6.24 instead. I cherry-picked them, so I'm fairly certain git will
> be smart enough to drop them from your 2.6.25 branch when you rebase.
>
> Please let me know if there are any problems.
>
> Thanks!
>
> John
>
> ---
>
> Individual patches are available here:
>
> http://www.kernel.org/pub//linux/kernel/people/linville/wireless-2.6/fixes-jgarzik/
>
pulled into #upstream-fixes; please check the merge in #upstream
prev parent reply other threads:[~2007-11-08 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 14:26 Please pull 'fixes-jgarzik' branch of wireless-2.6 (3rd time is the charm?) John W. Linville
[not found] ` <20071108142626.GH11957-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-11-08 17:53 ` Jeff Garzik [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=20071108175328.GA3491@havoc.gtf.org \
--to=jeff-o2qlijkoznsdnm+yrofe0a@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@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).