From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] backlight: report error on failure
Date: Mon, 20 Feb 2017 20:52:41 +0000 [thread overview]
Message-ID: <20170220205241.GA10427@sudip-tp> (raw)
In-Reply-To: <20170219082618.GB30444@wychelm.lan>
On Sun, Feb 19, 2017 at 08:26:18AM +0000, Daniel Thompson wrote:
> On Sat, Feb 18, 2017 at 04:31:43PM +0000, Sudip Mukherjee wrote:
> > On Monday 30 January 2017 11:04 PM, Sudip Mukherjee wrote:
> > > On Wednesday 18 January 2017 09:23 PM, Sudip Mukherjee wrote:
> > > > It is possible to update the backlight power and the brightness using
> > > > the sysfs and on writing it either returns the count or if the callback
> > > > function does not exist then returns the error code 'ENXIO'.
> > > >
> > > > We have a situation where the userspace client is writing to the sysfs
> > > > to update the power and since the callback function exists the client
> > > > receives the return value as count and considers the operation to be
> > > > successful. That is correct as the write to the sysfs was successful.
> > > > But there is no way to know if the actual operation was done or not.
> > > >
> > > > backlight_update_status() returns the error code if it fails. Pass that
> > > > to the userspace client who is trying to update the power so that the
> > > > client knows that the operation failed.
> > > >
> > > > Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> > > > ---
> > >
> > > A gentle ping.
> >
> > Hi Andrew,
> >
> > Its more than one month now that this patch was submitted. Can you please
> > take it through your tree... else it will miss the merge window.
>
> Sorry you've been waiting so long for a review. Your "gentle ping" did
> result in a few minor tweaks to the maintainers but what it didn't
> (until today) provoke was review!
what tweaks? I can see that now you are the new maintainer.Is that the
result of my ping? :)
>
> To be honest, the ABI changes in the patch meant I wanted to check a
> few things first. However prompted by this mail I've just replied with
> the review I *should* have sent out a week ago [asking you rather than
> me to fill in some details about the likely effect of the ABI change ;-) ].
>
> BTW, I did do some archeology eariler in the week and I think the kernel
> has been swallowing error codes here for >10 years, so I'm curious if this
> is a theoretic bug fix or are you aware of some tangible problem in
> userspace that results from it?
I will reply to your other mail later this week. I am on a short holiday
now with very limited access.
But the problem that prompted me to send this patch is the current project
that I am working on now. And we faced this there. The userspace code is
writing to the sysfs node to poweron the backlight and reported success.
But sometimes we noticed that backlight was not actally powered on. And
that lead me to check the code and noticed that it is swallowing all the
errors.
Regards
Sudip
next prev parent reply other threads:[~2017-02-20 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 21:23 [PATCH] backlight: report error on failure Sudip Mukherjee
2017-01-30 23:04 ` Sudip Mukherjee
2017-02-18 16:31 ` Sudip Mukherjee
2017-02-19 8:26 ` Daniel Thompson
2017-02-20 20:52 ` Sudip Mukherjee [this message]
2017-02-22 8:52 ` Lee Jones
2017-02-08 12:54 ` Lee Jones
2017-02-19 8:13 ` Daniel Thompson
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=20170220205241.GA10427@sudip-tp \
--to=sudipm.mukherjee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.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;
as well as URLs for NNTP newsgroup(s).