From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tty/serial/pl011: don't print error msg if dmaengine_pause is not supported
Date: Tue, 19 Apr 2011 02:27:36 +0200 [thread overview]
Message-ID: <BANLkTi=rhN1v0t00wUU3KrC5yATbWK9D5Q@mail.gmail.com> (raw)
In-Reply-To: <98422bc7c3ebb4bf6a4ab26179b3f3b7d1a5b5ca.1303125086.git.viresh.kumar@st.com>
2011/4/18 Viresh Kumar <viresh.kumar@st.com>:
> Few dma controller doesn't support dmaengine_pause() and return -ENXIO if
> dmaengine_pause() is called for them. Error messages such as "unable to pause
> DMA transfer" shouldn't be printed for them.
Hm for dw_dma this seems like a piece of cake to simply implement
instead.
I'll send a patch for that instead, can you test it and ACK it if it
works for you?
Yours,
Linus Walleij
prev parent reply other threads:[~2011-04-19 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 11:22 [PATCH] tty/serial/pl011: don't print error msg if dmaengine_pause is not supported Viresh Kumar
2011-04-18 15:13 ` Russell King - ARM Linux
2011-04-19 6:07 ` viresh kumar
2011-04-19 0:27 ` Linus Walleij [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='BANLkTi=rhN1v0t00wUU3KrC5yATbWK9D5Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--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).