linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	"Igor M. Liplianin" <liplianin@netup.ru>
Subject: Re: linux-next: build failure after merge of the staging.current tree
Date: Wed, 8 Jun 2011 09:11:27 -0700	[thread overview]
Message-ID: <20110608161127.GD21645@kroah.com> (raw)
In-Reply-To: <20110608114130.444a7f99.sfr@canb.auug.org.au>

On Wed, Jun 08, 2011 at 11:41:30AM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the staging.current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/media/video/cx23885/cx23885-cards.c:28:28: fatal error: staging/altera.h: No such file or directory
> 
> Caused by commit 85ab9ee946da ("Staging: altera: move .h file to proper
> place").
> 
> I have used the staging.current tree from next-20110607 for today.

Ok, sorry about that.

Mauro, Igor, why would another driver need to reference a .h file of a
staging driver?  I'll patch it right now to point to the proper place
(down in the staging tree), but it would be good to resolve this
"properly" somehow.

Next time, please never include a staging driver that isn't
self-contained, and don't create include/staging/ that's not acceptable.

thanks,

greg k-h

  reply	other threads:[~2011-06-08 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  1:41 linux-next: build failure after merge of the staging.current tree Stephen Rothwell
2011-06-08 16:11 ` Greg KH [this message]
2011-06-08 16:58   ` Mauro Carvalho Chehab
2011-06-08 16:21 ` Greg KH
2017-12-14  6:00 Stephen Rothwell
2017-12-14  7:27 ` 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=20110608161127.GD21645@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=liplianin@netup.ru \
    --cc=mchehab@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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).