linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Vaussard <florian.vaussard-p8DiymsW2f8@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: "Benoit Cousson" <b-cousson-l0cyMroinI0@public.gmane.org>,
	"Tony Lindgren" <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Ben Dooks" <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	"Philippe Rétornaz"
	<philippe.retornaz-p8DiymsW2f8@public.gmane.org>
Subject: Re: [PATCH] omap-i2c: fix incorrect log message when using a device tree
Date: Tue, 11 Sep 2012 09:01:55 +0200	[thread overview]
Message-ID: <504EE1E3.7040304@epfl.ch> (raw)
In-Reply-To: <5040AFCC.5060004-l0cyMroinI0@public.gmane.org>

Hello Wolfram,

>> When booting using a device tree, the adapter number is dynamically
>> assigned after the log message is sent.
>> This patch modifies the log message to get a correct adapter id.
>>
>> Applies on 3.6-rc3. Tested on OMAP3 (Gumstix Overo).
>
> Thanks for the fix. Tested successfully on OMAP4 SDP DT boot as well.
>
> [    0.000000] Linux version 3.6.0-rc3-00030-g491038d (bcousson@lnwes3201) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #6 SMP Fri Aug 31 13:50:48 CEST 2012
> [    0.000000] CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7d
> [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> [    0.000000] Machine: Generic OMAP4 (Flattened Device Tree), model: TI OMAP4 SDP board
> ...
> [    0.667205] omap_i2c i2c.15: bus 0 rev2.4.0 at 400 kHz
> ...
> [    0.768341] omap_i2c i2c.16: bus 1 rev2.4.0 at 400 kHz
> [    0.783905] omap_i2c i2c.17: bus 2 rev2.4.0 at 400 kHz
> [    0.799530] omap_i2c i2c.18: bus 3 rev2.4.0 at 400 kHz
>
>
>> Signed-off-by: Florian Vaussard <florian.vaussard-p8DiymsW2f8@public.gmane.org>
>
> Tested-by: Benoit Cousson <b-cousson-l0cyMroinI0@public.gmane.org>
> and
> Acked-by: Benoit Cousson <b-cousson-l0cyMroinI0@public.gmane.org>
>
> Regards,
> Benoit
>

Was this patch picked-up by the i2c-embedded subsystem?

Thank you.

Regards,
Florian

  parent reply	other threads:[~2012-09-11  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31 11:02 [PATCH] omap-i2c: fix incorrect log message when using a device tree Florian Vaussard
2012-08-31 12:36 ` Benoit Cousson
     [not found]   ` <5040AFCC.5060004-l0cyMroinI0@public.gmane.org>
2012-09-11  7:01     ` Florian Vaussard [this message]
2012-09-11  9:28 ` Shubhrajyoti
     [not found] ` <1346410975-29930-1-git-send-email-florian.vaussard-p8DiymsW2f8@public.gmane.org>
2012-09-12 13:55   ` Wolfram Sang

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=504EE1E3.7040304@epfl.ch \
    --to=florian.vaussard-p8diymsw2f8@public.gmane.org \
    --cc=b-cousson-l0cyMroinI0@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=philippe.retornaz-p8DiymsW2f8@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).