From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Serge Semin <Sergey.Semin@baikalelectronics.ru>,
dmaengine <dmaengine@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v1 1/3] dmaengine: dw: Remove error message from DT parsing code
Date: Wed, 4 Aug 2021 14:03:49 +0300 [thread overview]
Message-ID: <CAHp75VfBtdKLDGvPVNQRs5acXVRTC2Ufk0aqJ4=X_0_w8yhMnw@mail.gmail.com> (raw)
In-Reply-To: <20210804094607.ac3zxomlmu3ifpqr@mobilestation>
On Wed, Aug 4, 2021 at 1:50 PM Serge Semin <fancer.lancer@gmail.com> wrote:
> On Mon, Aug 02, 2021 at 09:43:53PM +0300, Andy Shevchenko wrote:
> > Users are a bit frightened of the harmless message that tells that
> > DT is missed on ACPI-based platforms. Remove it for good, it will
> > simplify the future conversion to fwnode and device property APIs.
>
> Thanks for the cleanup patchset. No comments from me, just the tags
> for the whole series:
> Reviewed-by: Serge Semin <fancer.lancer@gmail.com>
> Tested-by: Serge Semin <fancer.lancer@gmail.com>
> [Tested on Baikal-T1 DW DMAC with 8 channels, 12 requests, 2 masters,
> no multi-block support and uneven max burst length setup]
Thank you, appreciate it!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-08-04 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 18:43 [PATCH v1 1/3] dmaengine: dw: Remove error message from DT parsing code Andy Shevchenko
2021-08-02 18:43 ` [PATCH v1 2/3] dmaengine: dw: Convert members to u32 in platform data Andy Shevchenko
2021-08-02 18:43 ` [PATCH v1 3/3] dmaengine: dw: Simplify DT property parser Andy Shevchenko
2021-08-04 9:46 ` [PATCH v1 1/3] dmaengine: dw: Remove error message from DT parsing code Serge Semin
2021-08-04 11:03 ` Andy Shevchenko [this message]
2021-08-06 13:49 ` Vinod Koul
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='CAHp75VfBtdKLDGvPVNQRs5acXVRTC2Ufk0aqJ4=X_0_w8yhMnw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vireshk@kernel.org \
--cc=vkoul@kernel.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).