public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	torvalds@linux-foundation.org
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Subject: Re: Fwd: Re: Broken builds
Date: Wed, 13 Jun 2012 13:20:09 +0300	[thread overview]
Message-ID: <1339582809.2637.20.camel@deskari> (raw)
In-Reply-To: <20120613095753.GA32099@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]

On Wed, 2012-06-13 at 10:57 +0100, Russell King - ARM Linux wrote:
> Linus,
> 
> Can you please apply the patch below.  I've been waiting 10 days so far
> for a fix for the build problem to get through the "normal" channels,
> and it seems to be stuck with the FBdev maintainer, who "missed -rc2"
> with his pull request - and still hasn't submitted it.

Note also that I sent the fix quite late, as I was on paternity leave.
So Florian didn't have many days to react.

> Tomi Valkeinen has a different fix to this, which is the one stuck in
> the fbdev maintainers tree.
> 
> I'm fed up with waiting for this build breakage to get fixed, and to
> think how badly I get flamed if I do something even sneeze wrongly in
> the direction of any x86 code...

Here's also my pull request, perhaps it's easier to pull it instead of
applying the patch.


The following changes since commit e92a5b28f71aea01b281f9c89d97a4bc5b24748f:

  OMAPDSS: HDMI: OMAP4: Update IRQ flags for the HPD IRQ request (2012-05-22 11:00:09 +0300)

are available in the git repository at:

  git://gitorious.org/linux-omap-dss2/linux.git tags/omapdss-for-3.5-rc2

for you to fetch changes up to c3a21fc79b6bc097d8b0e47498903a649a111127:

  OMAPDSS: fix registration of DPI and SDI devices (2012-06-05 17:15:24 +0300)

----------------------------------------------------------------
Small fixes for omapdss driver. Most importantly, fixes a build problem when
debugfs or omapdss debug support is turned off, and fixes a suspend related
crash.

----------------------------------------------------------------
Archit Taneja (1):
      OMAPDSS: DSI: Fix bug when calculating LP command interleaving parameters

Tomi Valkeinen (4):
      OMAPDSS: fix build when DEBUG_FS or DSS_DEBUG_SUPPORT disabled
      OMAPDSS: Taal: fix compilation warning
      OMAPDSS: fix bogus WARN_ON in dss_runtime_put()
      OMAPDSS: fix registration of DPI and SDI devices

 arch/arm/mach-omap2/display.c             |    4 ++--
 drivers/video/omap2/displays/panel-taal.c |    2 +-
 drivers/video/omap2/dss/core.c            |    3 +--
 drivers/video/omap2/dss/dsi.c             |    2 +-
 drivers/video/omap2/dss/dss.c             |    2 +-
 5 files changed, 6 insertions(+), 7 deletions(-)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-06-13 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  9:57 Fwd: Re: Broken builds Russell King - ARM Linux
2012-06-13 10:20 ` Tomi Valkeinen [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=1339582809.2637.20.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    /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