From: Greg KH <gregkh@suse.de>
To: Grant Coady <gcoady@gmail.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
LKML List <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.6.15-mm2 allyesconfig build failure in drivers/usb/ip/
Date: Tue, 10 Jan 2006 08:53:47 -0800 [thread overview]
Message-ID: <20060110165347.GA21240@suse.de> (raw)
In-Reply-To: <aoj7s1pmcvup9h47bnglk267s64vpm53a3@4ax.com>
On Wed, Jan 11, 2006 at 02:15:20AM +1100, Grant Coady wrote:
> On Tue, 10 Jan 2006 14:46:08 +0100, Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
> >allyesconfig currently doesn't build completely for me in 2.6.15-mm2
>
> I sent a patch http://lkml.org/lkml/2006/1/7/272
And I seem to have lost that one, care to bounce it to me?
Hm, no, wait, that patch is wrong, you want to be able to build both
drivers, and even into the kernel too. The code is wrong, I'll work on
fixing it...
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-10 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 13:46 2.6.15-mm2 allyesconfig build failure in drivers/usb/ip/ Jesper Juhl
2006-01-10 15:15 ` Grant Coady
2006-01-10 16:53 ` Greg KH [this message]
2006-01-10 15:26 ` [linux-usb-devel] " Alan Stern
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=20060110165347.GA21240@suse.de \
--to=gregkh@suse.de \
--cc=gcoady@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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