From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: regcache_sync() errors for read-only registers cache
Date: Mon, 02 Mar 2015 20:15:23 +0100 [thread overview]
Message-ID: <s5h7fuz8b3o.wl-tiwai@suse.de> (raw)
In-Reply-To: <20150302182418.GD21293@sirena.org.uk>
At Mon, 2 Mar 2015 18:24:18 +0000,
Mark Brown wrote:
>
> On Fri, Feb 27, 2015 at 01:59:30PM +0100, Takashi Iwai wrote:
>
> > A quick fix is the patch like below, but obviously it doesn't cover
> > the all cases but only addresses the signle rw.
>
> Please don't bury patches in the middle of mails, that just means that
> if the patch is useful it's painful to apply.
The --scissors option of git am is your friend.
> Your patch seems fine but
> can you please resend in a directly applyable format unless something in
> the below indicates against that...
Hm, so do you think that my patch is the best way to fix? I wasn't
sure about it, that's why I wrote in that style.
> > Also, _regmap_write() itself calls again regmap_writeable(), so it's
> > superfluous. Alternatively, we may check -EIO from _regmap_write()
> > and treat as a special case not to show the error. Or, add a
> > parameter to skip regmap_writeable() call.
>
> I'm sorry but I can't parse the above - what is "it" in this context?
regmap_wrietable() call in _regmap_write().
> Silently ignoring -EIO from the physical register write sounds like a
> very bad idea though, that seems likely to discard actual errors.
Right, in that case, a special error code might be used. But this
sounds like an overkill, too.
thanks,
Takashi
next prev parent reply other threads:[~2015-03-02 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 12:59 Takashi Iwai
2015-03-02 18:24 ` Mark Brown
2015-03-02 19:15 ` Takashi Iwai [this message]
2015-03-03 9:09 ` Mark Brown
2015-03-03 9:22 ` Takashi Iwai
2015-03-03 14:54 ` Mark Brown
2015-03-03 15:33 ` Takashi Iwai
2015-03-03 20:04 ` Mark Brown
2015-03-03 22:00 ` Takashi Iwai
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=s5h7fuz8b3o.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®