All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Denis CIOCCA <denis.ciocca@st.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/6] iio: st_sensors: announce registered sensors
Date: Sat, 26 Apr 2014 11:51:51 +0100	[thread overview]
Message-ID: <535B8FC7.7010308@kernel.org> (raw)
In-Reply-To: <CACRpkda1tZNF6gGo+HMaYmKnzuRHBMz6PRVeN+K5m8JessOrqw@mail.gmail.com>

On 24/04/14 09:30, Linus Walleij wrote:
> On Wed, Apr 23, 2014 at 11:21 PM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 13/04/14 20:08, Linus Walleij wrote:
>>>
>>> It is pretty helpful to know already from dmesg that a certain
>>> device is successfully registered, instead of having to browse
>>> sysfs to see if it's actually there.
>>>
>>> Cc: Lee Jones <lee.jones@linaro.org>
>>> Cc: Denis CIOCCA <denis.ciocca@st.com>
>>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>>
>>
>> hmm.. Normally I get irritated with these sorts of I'm here
>> messages - it's not exactly hard to tell it has been successfully
>> probed without filling the logs with messages fairly light on
>> info.  Having said that I tend to let these go in new drivers
>> so I don't care that strongly...
>
> Your pick, this patch is orthogonal to the rest.
>
> I tend to stick a oneliner at the end of successful probe
> to verify that the device driver has been compiled in and
> that it probes correctly so that the device tree etc is in
> order. Of course there are other ways to determine that
> but the dmesg give it all in one place for all devices.
>
Fair enough I suppose. Applied to the togreg branch of iio.git.
Will initially be pushed out as testing for the autobuilders
to play around with it.



  reply	other threads:[~2014-04-26 10:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 19:08 [PATCH 0/6] iio: enable ST Sensors on Ux500 Linus Walleij
2014-04-13 19:08 ` [PATCH 1/6] iio: st_sensors: announce registered sensors Linus Walleij
2014-04-23 21:21   ` Jonathan Cameron
2014-04-24  8:30     ` Linus Walleij
2014-04-26 10:51       ` Jonathan Cameron [this message]
2014-04-13 19:08 ` [PATCH 2/6] iio: st_sensors: move regulator retrieveal to core Linus Walleij
2014-04-13 19:09 ` [PATCH 3/6] iio: st_sensors: get platform data from device tree Linus Walleij
2014-04-26 10:56   ` Jonathan Cameron
2014-04-13 19:09 ` [PATCH 4/6] iio: st_sensors: add device tree bindings Linus Walleij
2014-04-13 19:09   ` Linus Walleij
2014-04-13 19:09 ` [PATCH 5/6] iio: st_sensors: add devicetree probing support Linus Walleij
2014-04-23 21:19   ` Jonathan Cameron
2014-04-24  8:33     ` Linus Walleij
2014-04-26 10:57       ` Jonathan Cameron
2014-06-02 12:07         ` Linus Walleij
2014-04-13 19:09 ` [PATCH 6/6] ARM: ux500: add misc sensors to the device trees Linus Walleij

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=535B8FC7.7010308@kernel.org \
    --to=jic23@kernel.org \
    --cc=denis.ciocca@st.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.