linux-kernel - Re: [PATCH] usb: musb: Kconfig: Depend on some machines under blackfin

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150405082908.GA25368@kroah.com>
Date:	Sun, 5 Apr 2015 10:29:08 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Chen Gang <xili_gchen_5257@...mail.com>
Cc:	Richard Weinberger <richard.weinberger@...il.com>, balbi@...com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org
Subject: Re: [PATCH] usb: musb: Kconfig: Depend on some machines under
 blackfin

On Sun, Apr 05, 2015 at 06:33:44AM +0800, Chen Gang wrote:
> On 4/4/15 17:54, Greg Kroah-Hartman wrote:
> > On Sat, Apr 04, 2015 at 05:51:21AM +0800, Chen Gang wrote:
> >> Under blackfin, only bf527, bf548 and bf609 may use musb. The related
> >> error with allmodconfig:
> >>
> >>     CC [M]  drivers/usb/misc/trancevibrator.o
> >>   In file included from drivers/usb/musb/musb_core.h:70:0,
> >>                    from drivers/usb/musb/musb_core.c:103:
> >>   drivers/usb/musb/musb_core.c: In function 'musb_indexed_ep_select':
> >>   drivers/usb/musb/musb_regs.h:458:32: error: 'USB_INDEX' undeclared (first use in this function)
> >>    #define MUSB_INDEX  USB_OFFSET(USB_INDEX) /* 8 bit */
> >>                                   ^
> >>
> >> Signed-off-by: Chen Gang <gang.chen.5i5j@...il.com>
> > 
> > Why not fix the root cause and provide this symbol on blackfin?  There's
> > no specific reason why it shouldn't be able to be built on this
> > platform.
> > 
> > It's better to make platforms properly build everything, patches like
> > this just make things messier and harder to maintain.
> > 
> 
> I am not quite sure all machines of blackfin can support musb (according
> to current code, at present, we can only sure bf527, bf548 and bf609 can
> support it).

What do you mean by "can support"?  What is missing?  Why doesn't the
code build there?

> So, I suggest to add new macro HAVE_MUSB for BLACKFIN in patch v2. And
> welcome any other members' idea.

I recommend fixing blackfin, what makes this one specific platform so
broken compared to the 20+ other platforms that don't need this special
treatment?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/