From: Evgeniy Polyakov <zbr@ioremap.net>
To: Paul Walmsley <paul@pwsan.com>
Cc: NeilBrown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] W1: OMAP HDQ1W: allow driver to be built on all OMAP2+
Date: Wed, 2 May 2012 19:34:32 +0400 [thread overview]
Message-ID: <20120502153432.GA15534@ioremap.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1205020206020.19695@utopia.booyaka.com>
On Wed, May 02, 2012 at 02:08:36AM -0600, Paul Walmsley (paul@pwsan.com) wrote:
>
> Allow the OMAP HDQ1W driver to be built for all OMAP2+ SoCs by
> adjusting KConfig dependencies. The previous dependency required
> either SOC_OMAP2430 or ARCH_OMAP3 to be set, but the HDQ IP block is
> present on OMAP2420 and OMAP44xx SoCs. The driver was still
> selectable on multi-OMAP kernel configurations, however; so the
> previous prohibition was rather pointless.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Evgeniy Polyakov <zbr@ioremap.net>
Well, looks good, although I know nothing about build deps for OMAP platform :)
--
Evgeniy Polyakov
WARNING: multiple messages have this Message-ID (diff)
From: zbr@ioremap.net (Evgeniy Polyakov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] W1: OMAP HDQ1W: allow driver to be built on all OMAP2+
Date: Wed, 2 May 2012 19:34:32 +0400 [thread overview]
Message-ID: <20120502153432.GA15534@ioremap.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1205020206020.19695@utopia.booyaka.com>
On Wed, May 02, 2012 at 02:08:36AM -0600, Paul Walmsley (paul at pwsan.com) wrote:
>
> Allow the OMAP HDQ1W driver to be built for all OMAP2+ SoCs by
> adjusting KConfig dependencies. The previous dependency required
> either SOC_OMAP2430 or ARCH_OMAP3 to be set, but the HDQ IP block is
> present on OMAP2420 and OMAP44xx SoCs. The driver was still
> selectable on multi-OMAP kernel configurations, however; so the
> previous prohibition was rather pointless.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> Cc: Evgeniy Polyakov <zbr@ioremap.net>
Well, looks good, although I know nothing about build deps for OMAP platform :)
--
Evgeniy Polyakov
next prev parent reply other threads:[~2012-05-02 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 8:08 [PATCH] W1: OMAP HDQ1W: allow driver to be built on all OMAP2+ Paul Walmsley
2012-05-02 8:08 ` Paul Walmsley
2012-05-02 15:34 ` Evgeniy Polyakov [this message]
2012-05-02 15:34 ` Evgeniy Polyakov
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=20120502153432.GA15534@ioremap.net \
--to=zbr@ioremap.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.