From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Lee Jones <lee.jones@linaro.org>, Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/7] staging: atomisp: Do not call dev_warn with a NULL device
Date: Sun, 28 May 2017 18:08:53 +0100 [thread overview]
Message-ID: <20170528180853.5a6c8f11@alans-desktop> (raw)
In-Reply-To: <20170528123040.18555-2-hdegoede@redhat.com>
On Sun, 28 May 2017 14:30:35 +0200
Hans de Goede <hdegoede@redhat.com> wrote:
> Do not call dev_warn with a NULL device, this silence the following 2
> warnings:
>
> [ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO
> [ 14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO
>
> We could switch to using pr_warn for dev == NULL instead, but as comments
> in the source indicate, the check for these 2 special gmin variables with
> a NULL device is a workaround for 2 specific evaluation boards, so
> completely silencing the missing warning for these actually is a good
> thing.
At which point real missing variables won't get reported so NAK. I think
the right fix is to make the offending callers pass
subdev->dev
which if my understanding of the subdevices is correct should pass the
right valid device field from the atomisp.
Please also cc me if you are proposing patches this driver - and also
linux-media.
Alan
next prev parent reply other threads:[~2017-05-28 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 12:30 [PATCH v5 1/7] staging: atomisp: Fix calling efivar_entry_get() with unaligned arguments Hans de Goede
2017-05-28 12:30 ` [PATCH v5 2/7] staging: atomisp: Do not call dev_warn with a NULL device Hans de Goede
2017-05-28 17:08 ` Alan Cox [this message]
2017-05-28 18:26 ` Hans de Goede
2017-05-28 20:00 ` Alan Cox
2017-05-28 12:30 ` [PATCH v5 3/7] staging: atomisp: Set step to 0 for mt9m114 menu control Hans de Goede
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=20170528180853.5a6c8f11@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wens@csie.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