public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	linux-omap@vger.kernel.org,
	"Víctor Manuel Jáquez Leal" <vjaquez@igalia.com>
Subject: Re: tidspbridge in drivers/staging
Date: Sun, 22 Apr 2012 09:16:19 -0700	[thread overview]
Message-ID: <20120422161619.GA26175@kroah.com> (raw)
In-Reply-To: <20120422095717.GA25053@n2100.arm.linux.org.uk>

On Sun, Apr 22, 2012 at 10:57:17AM +0100, Russell King - ARM Linux wrote:
> I've noticed these failure from time to time in my omap4 randconfig builds:
> 
> drivers/staging/tidspbridge/core/tiomap3430.c: In function 'bridge_brd_start':
> drivers/staging/tidspbridge/core/tiomap3430.c:425: error: implicit declaration of function 'OMAP2_L4_IO_ADDRESS'
> drivers/staging/tidspbridge/core/wdt.c: In function 'dsp_wdt_init':
> drivers/staging/tidspbridge/core/wdt.c:56: error: implicit declaration of function 'OMAP2_L4_IO_ADDRESS'
> 
> Looking at git, it looks like there is some activity with tidspbridge
> (by Víctor).  Is there any interest in fixing these errors for v3.4
> (or even v3.4-rc5)?

Along those lines, what's the plans on getting this code _out_ of
staging?  I haven't seen anything going on here in a while...

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-04-22 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22  9:57 tidspbridge in drivers/staging Russell King - ARM Linux
2012-04-22 16:16 ` Greg KH [this message]
     [not found] ` <4f946a04b4288_274134788452074@nysa.mail>
2012-04-22 22:19   ` 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=20120422161619.GA26175@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=vjaquez@igalia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox