devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	Michal Simek
	<michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Re: Call for testing: device nodes as kobjects
Date: Wed, 17 Apr 2013 18:20:26 +0100	[thread overview]
Message-ID: <CACxGe6vZEXa9n332DmxqQsJLM9fdBFF5nFpf_W+AS4DRxkw2xw@mail.gmail.com> (raw)
In-Reply-To: <20130417171618.GW1906-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

On Wed, Apr 17, 2013 at 6:16 PM, Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> wrote:
> Hi Grant,
>
> On Wed, Apr 17, 2013 at 04:48:22PM +0100, Grant Likely wrote:
>> Hi folks,
>>
>> Could I get some testing support please? I've applied the patch that
>> makes device nodes into kobjects into the following branch and build
>> tested it on a bunch of platforms. What I need now is boot testing on
>> different architectures.
>>
>> If you can build this tree and make sure it doesn't break your
>> platforms with OF support I would greatly appreciate it.
>>
>> Also, if you turn off CONFIG_PROC_DEVICETREE, a symlink will be
>> created to the /sys/firmware  representation which should be
>> functionally identical. For those of you using tools that read
>> /proc/device-tree (like kexec), I would also appreciate if you can
>> test that those tools still work with CONFIG_PROC_DEVICETREE turned
>> off.
>>
>> git://git.secretlab.ca/git/linux devicetree/experimental
>
> I gave it a quick test on i.MX53 (qsb) and i.MX27 (phycore i.MX27).
> Both seem to work just normally. I also made a
>
> diff -urN /proc/device-tree /sys/firmware/ofw/device-tree
>
> with CONFIG_PROC_DEVICETREE enabled (so no symlink). Indeed both
> trees are identical.
>
> So:
>
> Tested-by: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Great, thanks!

g.

  parent reply	other threads:[~2013-04-17 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 15:48 Call for testing: device nodes as kobjects Grant Likely
     [not found] ` <CACxGe6vPsGK1PwF6xOkkTB5LD8DqgB+Ym7daCMoPbMbVMVBQtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-17 17:16   ` Sascha Hauer
     [not found]     ` <20130417171618.GW1906-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-17 17:20       ` Grant Likely [this message]
2013-04-17 17:22   ` Grant Likely
     [not found] ` <517963BB.5030308@linux.vnet.ibm.com>
     [not found]   ` <517963BB.5030308-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2013-04-25 21:35     ` Grant Likely

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=CACxGe6vZEXa9n332DmxqQsJLM9fdBFF5nFpf_W+AS4DRxkw2xw@mail.gmail.com \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
    --cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@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).