linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Gordon Farquharson <gordonfarquharson@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	"John W. Linville" <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: pull request: wireless-2.6 2008-02-27
Date: Sun, 23 Mar 2008 21:51:26 +0100	[thread overview]
Message-ID: <20080323205126.GB5087@uranus.ravnborg.org> (raw)
In-Reply-To: <97a0a9ac0803172107s2ac19268h3b297bb645011a3@mail.gmail.com>

On Mon, Mar 17, 2008 at 10:07:56PM -0600, Gordon Farquharson wrote:
> Hi Sam
> 
> On Sun, Mar 2, 2008 at 5:58 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
> 
> >  So please let me know if this works and then I can push it upstrem
> >  hopefully already by tomorrow.
> >
> >  Note: I decided to name the variable KBUILD_BUILDHOST as this is more
> >  descriptive then SUBARCH. We can later clean up the naming and get rid
> >  of SUBARCH but I refrained from this to make the pacht minimal.
> 
> What is the status of this patch? Is there any chance that it will be
> included in 2.6.25?

Thanks for your paitience.
I have been outright busy so I never came around to this.
It is pushed for inclusion in 2.6.25 now.

	Sam

  reply	other threads:[~2008-03-23 20:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28  1:41 pull request: wireless-2.6 2008-02-27 John W. Linville
2008-02-28  7:51 ` David Miller
2008-02-28 14:51   ` pull request: wireless-2.6 2008-02-28 John W. Linville
2008-02-28 19:22     ` David Miller
2008-02-28 21:21   ` pull request: wireless-2.6 2008-02-27 Gordon Farquharson
2008-02-28 21:30     ` David Miller
2008-02-28 23:56       ` Gordon Farquharson
2008-02-29  0:15         ` David Miller
2008-02-29 12:16       ` Michael Buesch
2008-02-29 16:26         ` John W. Linville
2008-02-29 16:34           ` Johannes Berg
2008-02-29 19:10             ` John W. Linville
2008-02-29 19:54               ` Johannes Berg
2008-02-29 21:42               ` John W. Linville
2008-03-01 13:01                 ` Sam Ravnborg
2008-03-01 15:51                   ` Michael Buesch
2008-03-02 11:58                     ` Sam Ravnborg
2008-03-02 20:00                       ` Gordon Farquharson
2008-03-02 20:25                         ` Michael Buesch
2008-03-18  4:07                       ` Gordon Farquharson
2008-03-23 20:51                         ` Sam Ravnborg [this message]
2008-03-23 21:23                           ` Gordon Farquharson
2008-03-01 22:59                   ` David Miller
2008-03-02 15:44                   ` Adrian Bunk
2008-02-29 23:13             ` Michael Buesch
2008-02-29 23:51               ` Randy Dunlap

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=20080323205126.GB5087@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=gordonfarquharson@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --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).