From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932127Ab2ENSgE (ORCPT ); Mon, 14 May 2012 14:36:04 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:61051 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757382Ab2ENSgB (ORCPT ); Mon, 14 May 2012 14:36:01 -0400 Date: Mon, 14 May 2012 11:35:57 -0700 From: Greg KH To: Reinhard Tartler Cc: Reinhard Tartler , Felipe Balbi , 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 Message-ID: <20120514183557.GA3832@kroah.com> References: <1337011520-15286-1-git-send-email-tartler@cs.fau.de> <20120514163154.GA17555@kroah.com> <87ipfyemb8.fsf@faui43f.informatik.uni-erlangen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ipfyemb8.fsf@faui43f.informatik.uni-erlangen.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > >> --- > >> 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