LKML Archive on
help / color / mirror / Atom feed
From: Dirk Behme <>
To: "Robert P. J. Day" <>
	Linux kernel mailing list <>
Subject: Re: definite OMAP1610_IR-related typo
Date: Sun, 28 Jan 2007 08:13:02 +0100	[thread overview]
Message-ID: <> (raw)

Robert P. J. Day wrote at LKML:
 > not sure what to do with this, it's all yours:
 > ========== OMAP1610_IR ==========
 > ./arch/arm/mach-omap1/devices.c:#if 
defined(CONFIG_OMAP1610_IR) ||
 > ========== OMAP161O_IR ==========
 > ./arch/arm/mach-omap1/devices.c:#if 
defined(CONFIG_OMAP1610_IR) ||
 > note first that one of those config vars has an "oh" 
while the other
 > has a *zero*. i'm pretty sure that's bad.
 > in any event, there's no such config variable of *either* 
 > in any Kconfig file, but there *is* a more all-encompassing
 > CONFIG_OMAP16XX confguration setting.

This is fixed in recent OMAP git tree and OMAP patches we 
prepared for upstream. Can you try OMAP patches 4113, 4114, 
4115 and 4116 to be found in RMKs patch system [1]? Or, even 
better, use current OMAP git [2]?



P.S. #1: Would be nice to CC OMAP list [3] next time as well.

P.S. #2: Sorry if mail references are wrong, I'm currently 
not subscribed to LKML.




             reply	other threads:[~2007-01-28  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28  7:13 Dirk Behme [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-27  8:31 Robert P. J. Day

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: definite OMAP1610_IR-related typo' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).