From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI
Date: Mon, 14 Nov 2016 09:55:51 +0800 [thread overview]
Message-ID: <20161114015549.GA3310@dragon> (raw)
In-Reply-To: <b68c1a07b6b5f027a6519c29b90217c1@agner.ch>
On Thu, Nov 10, 2016 at 08:27:50PM -0800, Stefan Agner wrote:
> You probably saw it, Dave merged it today in his drm-next branch:
> https://cgit.freedesktop.org/~airlied/linux/?h=drm-next
>
> I guess with that Shawn can go ahead and merge this patchset for next
> too...?
I merged #2 and #3 a couple of weeks ago. But for the first one, I have
to wait for the drm changes to appear on my tree, i.e. v4.10-rc1 likely.
Otherwise, HDMI will stop working on my tree if I apply that patch right
now.
So please ping me when drm changes are in place.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Stefan Agner <stefan-XLVq0VzYD2Y@public.gmane.org>
Cc: Vladimir Zapolskiy
<vladimir_zapolskiy-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>,
Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
marcel.ziswiler-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI
Date: Mon, 14 Nov 2016 09:55:51 +0800 [thread overview]
Message-ID: <20161114015549.GA3310@dragon> (raw)
In-Reply-To: <b68c1a07b6b5f027a6519c29b90217c1-XLVq0VzYD2Y@public.gmane.org>
On Thu, Nov 10, 2016 at 08:27:50PM -0800, Stefan Agner wrote:
> You probably saw it, Dave merged it today in his drm-next branch:
> https://cgit.freedesktop.org/~airlied/linux/?h=drm-next
>
> I guess with that Shawn can go ahead and merge this patchset for next
> too...?
I merged #2 and #3 a couple of weeks ago. But for the first one, I have
to wait for the drm changes to appear on my tree, i.e. v4.10-rc1 likely.
Otherwise, HDMI will stop working on my tree if I apply that patch right
now.
So please ping me when drm changes are in place.
Shawn
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
maitysanchayan@gmail.com, marcel.ziswiler@toradex.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI
Date: Mon, 14 Nov 2016 09:55:51 +0800 [thread overview]
Message-ID: <20161114015549.GA3310@dragon> (raw)
In-Reply-To: <b68c1a07b6b5f027a6519c29b90217c1@agner.ch>
On Thu, Nov 10, 2016 at 08:27:50PM -0800, Stefan Agner wrote:
> You probably saw it, Dave merged it today in his drm-next branch:
> https://cgit.freedesktop.org/~airlied/linux/?h=drm-next
>
> I guess with that Shawn can go ahead and merge this patchset for next
> too...?
I merged #2 and #3 a couple of weeks ago. But for the first one, I have
to wait for the drm changes to appear on my tree, i.e. v4.10-rc1 likely.
Otherwise, HDMI will stop working on my tree if I apply that patch right
now.
So please ping me when drm changes are in place.
Shawn
next prev parent reply other threads:[~2016-11-14 1:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 5:11 [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI Sanchayan Maity
2016-09-19 5:11 ` Sanchayan Maity
2016-09-19 5:11 ` [PATCH v2 2/3] ARM: dts: imx6q-apalis-ixora: Remove use of pwm-leds Sanchayan Maity
2016-09-19 5:11 ` Sanchayan Maity
2016-10-22 3:32 ` Shawn Guo
2016-10-22 3:32 ` Shawn Guo
2016-09-19 5:11 ` [PATCH v2 3/3] ARM: dts: imx6qdl-apalis: Use enable-gpios property for backlight Sanchayan Maity
2016-09-19 5:11 ` Sanchayan Maity
2016-09-19 5:11 ` Sanchayan Maity
2016-10-22 3:32 ` Shawn Guo
2016-10-22 3:32 ` Shawn Guo
2016-09-27 4:19 ` [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI maitysanchayan at gmail.com
2016-09-27 4:19 ` maitysanchayan
2016-09-27 4:19 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-09-27 6:28 ` Marcel Ziswiler
2016-09-27 6:28 ` Marcel Ziswiler
2016-09-27 6:28 ` Marcel Ziswiler
2016-10-22 3:25 ` Shawn Guo
2016-10-22 3:25 ` Shawn Guo
2016-10-22 3:25 ` Shawn Guo
2016-10-22 12:43 ` Vladimir Zapolskiy
2016-10-22 12:43 ` Vladimir Zapolskiy
2016-10-22 12:43 ` Vladimir Zapolskiy
2016-11-08 17:33 ` maitysanchayan at gmail.com
2016-11-08 17:33 ` maitysanchayan
2016-11-08 17:33 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-11-09 0:50 ` Stefan Agner
2016-11-09 0:50 ` Stefan Agner
2016-11-10 18:29 ` Vladimir Zapolskiy
2016-11-10 18:29 ` Vladimir Zapolskiy
2016-11-10 18:29 ` Vladimir Zapolskiy
2016-11-11 4:27 ` Stefan Agner
2016-11-11 4:27 ` Stefan Agner
2016-11-14 1:55 ` Shawn Guo [this message]
2016-11-14 1:55 ` Shawn Guo
2016-11-14 1:55 ` Shawn Guo
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=20161114015549.GA3310@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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.