All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomoya MORINAGA <tomoya.rohm@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	qi.wang@intel.com, yong.y.wang@intel.com, joel.clark@intel.com,
	kok.howg.ewe@intel.com
Subject: Re: [PATCH][linux-next][RESEND] usb/gadget/pch_udc: Fix compile error
Date: Tue, 6 Mar 2012 06:58:17 -0800	[thread overview]
Message-ID: <20120306145817.GA2947@kroah.com> (raw)
In-Reply-To: <CANKRQng9mXsotS=Lq9QwwmXWEdfrwPUcTdxvjOf56uXe7APMiQ@mail.gmail.com>

On Tue, Mar 06, 2012 at 03:39:37PM +0900, Tomoya MORINAGA wrote:
> Hi
> 
> Add information.
> 
> My develop environment is on x86.
> 
> According to following report,
>   http://kisskb.ellerman.id.au/kisskb/buildresult/5771890/
>   http://kisskb.ellerman.id.au/kisskb/buildresult/5771905/
> 
> This occurred on sparc64.
> 
> I suspect this issue ins GPIO implementation for sparc64.
> Does sparc64 support GPIO interrupt ?
> (Even x86, before 2.6.39, GPIO interrupt is not implemented !)
> 
> Additionally, this driver is for companion chip of Intel Atom E6xx series.
> So, this driver is never used for except x86, e.g. sparc.

Then the Kconfig file should probably only enable it on x86 to prevent
these kinds of things :)

thanks,

greg k-h

  reply	other threads:[~2012-03-06 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 22:01 "usb: gadget: pch_udc: Detecting VBUS through GPIO with interrupt" breaks sparc Paul Gortmaker
2012-03-02 23:41 ` Stephen Rothwell
2012-03-05 16:43   ` Greg KH
2012-03-06  0:07     ` Tomoya MORINAGA
2012-03-06  2:35       ` [PATCH][linux-next] usb/gadget/pch_udc: Fix compile error Tomoya MORINAGA
2012-03-06  2:49     ` [PATCH][linux-next][RESEND] " Tomoya MORINAGA
2012-03-06  6:39       ` Tomoya MORINAGA
2012-03-06 14:58         ` Greg Kroah-Hartman [this message]
2012-03-07  0:44           ` Tomoya MORINAGA

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=20120306145817.GA2947@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@ti.com \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=qi.wang@intel.com \
    --cc=tomoya.rohm@gmail.com \
    --cc=yong.y.wang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.