From: Greg KH <gregkh@linuxfoundation.org>
To: Reinhard Tartler <Reinhard.Tartler@informatik.uni-erlangen.de>
Cc: Reinhard Tartler <tartler@cs.fau.de>, Felipe Balbi <balbi@ti.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
vamos-dev@lists.cs.fau.de
Subject: Re: [PATCH] usb: musb: cppi: add missing include to fix compilation
Date: Mon, 14 May 2012 11:35:57 -0700 [thread overview]
Message-ID: <20120514183557.GA3832@kroah.com> (raw)
In-Reply-To: <87ipfyemb8.fsf@faui43f.informatik.uni-erlangen.de>
On Mon, May 14, 2012 at 06:53:31PM +0200, Reinhard Tartler wrote:
> On Mo, Mai 14, 2012 at 18:31:54 (CEST), Greg KH wrote:
>
> > On Mon, May 14, 2012 at 06:05:20PM +0200, Reinhard Tartler wrote:
> >> This fixes compilation as module.
> >>
> >> Signed-off-by: Reinhard Tartler <tartler@cs.fau.de>
> >> ---
> >> drivers/usb/musb/cppi_dma.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> This patch was found by tools developed in the VAMOS project:
> >> http://www4.cs.fau.de/Research/VAMOS/
> >
> > Does that mean that no one actually can hit this in "real life"? Or is
> > there a valid .config that this solves a problem for? If so, is it also
> > needed for the 3.4/3.3-stable tree and older ones?
>
> My tool has generated the attached configuration that exposes this
> compilation failure. I have used kernel v3.2 with Ubuntu's arm
> cross-compiler for the analysis and verification.
Does this show up on the 3.4-rc kernels? 3.3? I can't do anything
about going back in time and fixing 3.2 right now, sorry.
greg k-h
prev parent reply other threads:[~2012-05-14 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:05 Reinhard Tartler
2012-05-14 16:31 ` Greg KH
2012-05-14 16:53 ` Reinhard Tartler
2012-05-14 17:26 ` Sergei Shtylyov
2012-05-14 18:35 ` Greg KH [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=20120514183557.GA3832@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tartler@cs.fau.de \
--cc=vamos-dev@lists.cs.fau.de \
/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
Powered by JetHome