From: Jon Hunter <jon-hunter@ti.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Rob Herring <robherring2@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH] of: dma: Fix-up for warnings !CONFIG_OF
Date: Fri, 30 Nov 2012 09:36:18 -0600 [thread overview]
Message-ID: <50B8D272.7000603@ti.com> (raw)
In-Reply-To: <1354232877.7077.74.camel@vkoul-udesk3>
On 11/29/2012 05:47 PM, Vinod Koul wrote:
> On Thu, 2012-11-29 at 16:24 -0600, Jon Hunter wrote:
>> When compiling the kernel with DMA engine support enabled and device-tree
>> support disabled, the following warnings are observed.
> Thanks, already committed same change last night.
Great! Thanks.
Jon
WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] of: dma: Fix-up for warnings !CONFIG_OF
Date: Fri, 30 Nov 2012 09:36:18 -0600 [thread overview]
Message-ID: <50B8D272.7000603@ti.com> (raw)
In-Reply-To: <1354232877.7077.74.camel@vkoul-udesk3>
On 11/29/2012 05:47 PM, Vinod Koul wrote:
> On Thu, 2012-11-29 at 16:24 -0600, Jon Hunter wrote:
>> When compiling the kernel with DMA engine support enabled and device-tree
>> support disabled, the following warnings are observed.
> Thanks, already committed same change last night.
Great! Thanks.
Jon
next prev parent reply other threads:[~2012-11-30 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 22:24 [PATCH] of: dma: Fix-up for warnings !CONFIG_OF Jon Hunter
2012-11-29 22:24 ` Jon Hunter
2012-11-29 23:47 ` Vinod Koul
2012-11-29 23:47 ` Vinod Koul
2012-11-30 15:36 ` Jon Hunter [this message]
2012-11-30 15:36 ` Jon Hunter
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=50B8D272.7000603@ti.com \
--to=jon-hunter@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=fengguang.wu@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=vinod.koul@linux.intel.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.