All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Kevin Hilman <khilman@kernel.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org,
	Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
	Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH] ARM: dts: Revert disabling of smc91x for n900
Date: Thu, 19 Feb 2015 11:59:57 +0100	[thread overview]
Message-ID: <201502191159.57981@pali> (raw)
In-Reply-To: <20150219045047.GE32521@atomide.com>

[-- Attachment #1: Type: Text/Plain, Size: 894 bytes --]

On Thursday 19 February 2015 05:50:48 Tony Lindgren wrote:
> * Pali Rohár <pali.rohar@gmail.com> [150218 15:58]:
> > On Wednesday 18 February 2015 23:42:06 Tony Lindgren wrote:
> > > Of course it's always possible to do do a
> > > omap3-n900-qemu.dts if larger changes are needed :)
> > 
> > I would like to avoid using separate DTS for qemu. When we
> > have only one DTS file (for both qemu and real HW), we can
> > test for regression in qemu and we are sure that we have
> > same software configuration...
> 
> Agreed, and I'd rather take the extra warning on rare to find
> hardware to avoid an etra .dts file.
> 
> Are there any reasons whey the n900 qemu support could not
> be in the mainline qemu btw?
> 
> Regards,
> 
> Tony

Missing lot of omap stuff (in mainline qemu) which linaro have 
not sent to mainline yet...

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-02-19 11:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 23:02 [PATCH] ARM: dts: Revert disabling of smc91x for n900 Tony Lindgren
2015-01-05 23:09 ` Pali Rohár
2015-01-05 23:10   ` Tony Lindgren
2015-01-06 15:03   ` Sebastian Reichel
2015-01-06 15:23     ` Pali Rohár
2015-01-06  8:00 ` Pavel Machek
2015-01-06 16:59   ` Tony Lindgren
2015-01-06 19:44     ` Aaro Koskinen
2015-01-06 19:54       ` Tony Lindgren
2015-01-06 20:17         ` Tony Lindgren
2015-01-06 20:34           ` Pali Rohár
2015-01-06 21:24             ` Tony Lindgren
2015-01-06 20:42           ` Pavel Machek
2015-01-06 21:56         ` Aaro Koskinen
2015-01-06 22:04           ` Tony Lindgren
2015-01-06 19:59       ` Pali Rohár
2015-01-07  9:57     ` Pavel Machek
2015-01-07 15:44       ` Nishanth Menon
2015-01-07 16:40         ` Tony Lindgren
2015-01-07 20:09           ` Pavel Machek
2015-01-07 21:25           ` Pavel Machek
2015-01-08  9:01           ` Pali Rohár
2015-01-08 18:54             ` Tony Lindgren
2015-01-07 20:00         ` Pavel Machek
2015-01-06 17:38 ` Kevin Hilman
2015-02-18 15:19 ` Pali Rohár
2015-02-18 16:33   ` Tony Lindgren
2015-02-18 19:04     ` Pali Rohár
2015-02-18 22:42       ` Tony Lindgren
2015-02-18 22:42         ` Tony Lindgren
2015-02-18 22:52         ` Pali Rohár
2015-02-19  4:50           ` Tony Lindgren
2015-02-19 10:59             ` Pali Rohár [this message]
2015-02-19 16:47         ` Pali Rohár

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=201502191159.57981@pali \
    --to=pali.rohar@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=pavel@ucw.cz \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /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.