From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dmaengine: qcom_hidma: correct overriding message
Date: Wed, 19 Jul 2017 09:39:18 +0530 [thread overview]
Message-ID: <20170719040917.GD3053@localhost> (raw)
In-Reply-To: <1500215438-30672-1-git-send-email-okaya@codeaurora.org>
On Sun, Jul 16, 2017 at 10:30:37AM -0400, Sinan Kaya wrote:
> A false overriding information is being presented during boot
> under this scenario.
>
> 1. First object checks for kernel command line value against zero.
> 2. It doesn't find it, it sets the command line variable to the
> value coming from ACPI/DT.
> 3. Second object is being probed.
> 4. Second object sees that the value of kernel command line
> override is non-zero, it prints an overriding message even though
> value matches ACPI/DT value.
>
> hidma-mgmt QCOM8060:03: overriding max-write-burst-bytes: 1024
>
> Add an additional check to verify that kernel command line value
> is different from the ACPI/DT value.
Applied both, thanks
--
~Vinod
prev parent reply other threads:[~2017-07-19 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 14:30 [PATCH 1/2] dmaengine: qcom_hidma: correct overriding message Sinan Kaya
2017-07-16 14:30 ` [PATCH 2/2] dmaengine: qcom_hidma: correct channel QOS register offset Sinan Kaya
2017-07-19 4:09 ` Vinod Koul [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=20170719040917.GD3053@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).