From: Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
To: Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
Cc: Alexey Dobriyan
<adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
Date: Tue, 4 Nov 2008 20:45:29 +0100 [thread overview]
Message-ID: <20081104194528.GI32133@tekkaman> (raw)
In-Reply-To: <20081104184334.GA1840-l3A5Bk7waGM@public.gmane.org>
On Tue, Nov 04, 2008 at 10:43:34AM -0800, Greg KH wrote:
> On Tue, Nov 04, 2008 at 05:30:38PM +0100, Rodolfo Giometti wrote:
> > On Mon, Nov 03, 2008 at 06:50:47PM +0300, Alexey Dobriyan wrote:
> > > On sparc:
> > >
> > > drivers/usb/host/oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
> > >
> > > and including linux/irq.h doesn't cut it CONFIG_GENERIC_HARDIRQS aren't set.
> >
> > Should I force CONFIG_GENERIC_HARDIRQS selection?
>
> Can this hardware work on SPARC?
I think so even if on the data sheet is not specified...
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org
Linux Device Driver giometti-k2GhghHVRtY@public.gmane.org
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-04 19:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 7:32 linux-next: Tree for November 3 Stephen Rothwell
2008-11-03 13:58 ` next-20081103: error: asm/ftrace.h: No such file or directory Alexey Dobriyan
2008-11-03 14:04 ` Ingo Molnar
2008-11-03 14:28 ` next-20081103: arch/arm/kernel/elf.c:30: error: 'e_flags' undeclared Alexey Dobriyan
2008-11-03 15:08 ` Mikael Pettersson
2008-11-03 15:31 ` Russell King
2008-11-03 14:54 ` next-20081103: voyager Alexey Dobriyan
2008-11-03 15:08 ` Ingo Molnar
2008-11-03 15:50 ` next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type' Alexey Dobriyan
[not found] ` <20081103155047.GA14489-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2008-11-04 16:30 ` Rodolfo Giometti
2008-11-04 18:43 ` Greg KH
[not found] ` <20081104184334.GA1840-l3A5Bk7waGM@public.gmane.org>
2008-11-04 19:45 ` Rodolfo Giometti [this message]
2008-11-05 8:50 ` Alexey Dobriyan
[not found] ` <20081103112018.5823291b.randy.dunlap@oracle.com>
2008-11-04 9:23 ` linux-next: Tree for November 3 (kvm)(resend/lost) Avi Kivity
2008-11-05 7:13 ` next-20081103 - possible circular locking dependency detected while bring up eth1 Kamalesh Babulal
2008-11-05 7:48 ` Peter Zijlstra
2008-11-05 9:14 ` KOSAKI Motohiro
2008-11-06 10:18 ` linux-next: Tree for November 3 Nico -telmich- Schottelius
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=20081104194528.GI32133@tekkaman \
--to=giometti-avvdyk/kqijwk0htik3j/w@public.gmane.org \
--cc=adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gregkh-l3A5Bk7waGM@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@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).