From: Louis Garcia <louisg00@bellsouth.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: USB compile error with latest 2.5-bk
Date: 24 Mar 2003 23:33:40 -0500 [thread overview]
Message-ID: <1048566820.2455.1.camel@tiger> (raw)
In-Reply-To: <1048514654.25136.6.camel@irongate.swansea.linux.org.uk>
just recompiled 2.5.66 and went fine. I must have messed a patch up.
--Lou
On Mon, 2003-03-24 at 09:04, Alan Cox wrote:
> On Mon, 2003-03-24 at 09:53, Greg KH wrote:
> > > drivers/usb/core/hcd.c:124: parse error before '>>' token
> > > drivers/usb/core/hcd.c:124: initializer element is not constant
> > > drivers/usb/core/hcd.c:124: (near initialization for
> > > `usb2_rh_dev_descriptor[12]')
> >
> > I don't see this error with a older compiler. I suggest filing a bug
> > with Red Hat's bugzilla.
>
> I don't get this error with a current compiler either. Are you sure the
> patching is ok ?
>
prev parent reply other threads:[~2003-03-25 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 23:34 USB compile error with latest 2.5-bk Louis Garcia
2003-03-24 9:53 ` Greg KH
2003-03-24 14:04 ` Alan Cox
2003-03-25 4:33 ` Louis Garcia [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=1048566820.2455.1.camel@tiger \
--to=louisg00@bellsouth.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@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