From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Reinhard Tartler <Reinhard.Tartler@informatik.uni-erlangen.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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 21:26:02 +0400 [thread overview]
Message-ID: <4FB1402A.4020609@mvista.com> (raw)
In-Reply-To: <87ipfyemb8.fsf@faui43f.informatik.uni-erlangen.de>
Hello.
On 05/14/2012 08:53 PM, Reinhard Tartler 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.
Strange, your .config indicated that DMA driver and MUSB driver into which
it is linked are build monolithic. You also should use 3.3 series kernel.
> Cheers,
> Reinhard
WBR, Sergei
next prev parent reply other threads:[~2012-05-14 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:05 [PATCH] usb: musb: cppi: add missing include to fix compilation Reinhard Tartler
2012-05-14 16:31 ` Greg KH
2012-05-14 16:53 ` Reinhard Tartler
2012-05-14 17:26 ` Sergei Shtylyov [this message]
2012-05-14 18:35 ` Greg KH
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=4FB1402A.4020609@mvista.com \
--to=sshtylyov@mvista.com \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).