From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
hexdump0815@googlemail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/1] ARM: meson8b-mxq: better support for the TRONFY MXQ
Date: Fri, 24 May 2019 12:42:13 -0700 [thread overview]
Message-ID: <7hblzr1vxm.fsf@baylibre.com> (raw)
In-Reply-To: <20190524181936.29470-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> A while ago a user asked on #linux-amlogic about the state of the
> TRONFY MXQ in mainline. I did some research (mainly downloading an
> Android firmware image for that device and looking at the .dtb) and
> updated the mainline .dts accordingly.
>
> I kept this patch in my tree but didn't hear back from anyone with one
> of these boards (who could actually test my patch). That was until
> today where I got the following message on IRC:
> any plans to submit your latest own version of the meson8b mxq dtb
> to mainline? it works really well for me and the one in mainline is
> too simple to be usedful ...
Any chance of getting a Tested-by: from that IRC user on the patch?
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
hexdump0815@googlemail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/1] ARM: meson8b-mxq: better support for the TRONFY MXQ
Date: Fri, 24 May 2019 12:42:13 -0700 [thread overview]
Message-ID: <7hblzr1vxm.fsf@baylibre.com> (raw)
In-Reply-To: <20190524181936.29470-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> A while ago a user asked on #linux-amlogic about the state of the
> TRONFY MXQ in mainline. I did some research (mainly downloading an
> Android firmware image for that device and looking at the .dtb) and
> updated the mainline .dts accordingly.
>
> I kept this patch in my tree but didn't hear back from anyone with one
> of these boards (who could actually test my patch). That was until
> today where I got the following message on IRC:
> any plans to submit your latest own version of the meson8b mxq dtb
> to mainline? it works really well for me and the one in mainline is
> too simple to be usedful ...
Any chance of getting a Tested-by: from that IRC user on the patch?
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, hexdump0815@googlemail.com,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH 0/1] ARM: meson8b-mxq: better support for the TRONFY MXQ
Date: Fri, 24 May 2019 12:42:13 -0700 [thread overview]
Message-ID: <7hblzr1vxm.fsf@baylibre.com> (raw)
In-Reply-To: <20190524181936.29470-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> A while ago a user asked on #linux-amlogic about the state of the
> TRONFY MXQ in mainline. I did some research (mainly downloading an
> Android firmware image for that device and looking at the .dtb) and
> updated the mainline .dts accordingly.
>
> I kept this patch in my tree but didn't hear back from anyone with one
> of these boards (who could actually test my patch). That was until
> today where I got the following message on IRC:
> any plans to submit your latest own version of the meson8b mxq dtb
> to mainline? it works really well for me and the one in mainline is
> too simple to be usedful ...
Any chance of getting a Tested-by: from that IRC user on the patch?
Kevin
next prev parent reply other threads:[~2019-05-24 19:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 18:19 [PATCH 0/1] ARM: meson8b-mxq: better support for the TRONFY MXQ Martin Blumenstingl
2019-05-24 18:19 ` Martin Blumenstingl
2019-05-24 18:19 ` Martin Blumenstingl
2019-05-24 18:19 ` [PATCH 1/1] ARM: dts: meson8b: mxq: improve support for the TRONFY MXQ S805 Martin Blumenstingl
2019-05-24 18:19 ` Martin Blumenstingl
2019-05-24 18:19 ` Martin Blumenstingl
2019-05-27 13:17 ` hex dump
2019-05-27 13:17 ` hex dump
2019-05-27 13:17 ` hex dump
[not found] ` <CAKTihDVyQqq82KKofCTKoUYJOyT6T738uq_A=kiEqahDx9YQfA@mail.gmail.com>
2019-06-03 22:18 ` Kevin Hilman
2019-06-03 22:18 ` Kevin Hilman
2019-06-03 22:18 ` Kevin Hilman
2019-05-24 19:42 ` Kevin Hilman [this message]
2019-05-24 19:42 ` [PATCH 0/1] ARM: meson8b-mxq: better support for the TRONFY MXQ Kevin Hilman
2019-05-24 19:42 ` Kevin Hilman
2019-05-24 19:52 ` Martin Blumenstingl
2019-05-24 19:52 ` Martin Blumenstingl
2019-05-24 19:52 ` Martin Blumenstingl
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=7hblzr1vxm.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=hexdump0815@googlemail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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.