linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-wireless@vger.kernel.org
Subject: Re: libertas driver
Date: Thu, 10 May 2007 23:14:24 -0400	[thread overview]
Message-ID: <1178853264.8607.61.camel@localhost.localdomain> (raw)
In-Reply-To: <4643D3FC.9070308@garzik.org>

On Thu, 2007-05-10 at 22:25 -0400, Jeff Garzik wrote:
> Andrew Morton wrote:
> > x86_64 build is a bit ugly.
> 
> Not sure what happened to his mailer (patch #0 of 19 appeared), but:
> http://people.redhat.com/dcbw/libertas-patches/
> 
> Patches 18 and 19 address several of these.

16, 18, and 19 should take care of all the issues I (and Randy) found by
sparse and building on x86-64.

Thanks,
Dan



      reply	other threads:[~2007-05-11  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11  1:14 libertas driver Andrew Morton
2007-05-11  2:25 ` Jeff Garzik
2007-05-11  3:14   ` Dan Williams [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=1178853264.8607.61.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-wireless@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).