From: Sam Ravnborg <sam@ravnborg.org>
To: Lee Jones <lee.jones@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: alexandre.belloni@bootlin.com, airlied@linux.ie,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
peda@axentia.se, boris.brezillon@bootlin.com,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Immutable branch between MFD and DRM due for the v5.6 merge window
Date: Tue, 7 Jan 2020 19:21:24 +0100 [thread overview]
Message-ID: <20200107182124.GB20555@ravnborg.org> (raw)
In-Reply-To: <20200107101748.GC14821@dell>
Hi Maarten.
On Tue, Jan 07, 2020 at 10:17:48AM +0000, Lee Jones wrote:
> The MFD parts for testing:
>
> The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
>
> Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/ib-mfd-drm-v5.6
>
> for you to fetch changes up to 10f9167664362bac6f44813687cf52fec9d15845:
>
> mfd: atmel-hlcdc: Return in case of error (2020-01-07 10:08:58 +0000)
>
> ----------------------------------------------------------------
> Immutable branch between MFD and DRM due for the v5.6 merge window
>
> ----------------------------------------------------------------
> Claudiu Beznea (2):
> mfd: atmel-hlcdc: Add struct device member to struct atmel_hlcdc_regmap
> mfd: atmel-hlcdc: Return in case of error
>
> drivers/mfd/atmel-hlcdc.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
Can we get this into drm-misc-next?
I am not familiar with the process how to do this, and hope you can
help.
Thanks in advance,
Sam
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-07 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 12:28 [PATCH v3 0/6] fixes for atmel-hlcdc Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 1/6] drm: atmel-hlcdc: use double rate for pixel clock only if supported Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 2/6] drm: atmel-hlcdc: enable clock before configuring timing engine Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 3/6] mfd: atmel-hlcdc: add struct device member to struct atmel_hlcdc_regmap Claudiu Beznea
2019-12-18 12:28 ` [PATCH v3 4/6] mfd: atmel-hlcdc: return in case of error Claudiu Beznea
2020-01-07 10:18 ` Lee Jones
2019-12-18 12:28 ` [PATCH v3 5/6] drm: atmel-hlcdc: prefer a lower pixel-clock than requested Claudiu Beznea
2020-01-02 9:08 ` Sam Ravnborg
2020-01-04 17:12 ` Sam Ravnborg
2020-01-06 9:25 ` Claudiu.Beznea
2020-01-06 19:02 ` Sam Ravnborg
2020-01-06 9:24 ` Claudiu.Beznea
2020-01-07 9:19 ` Peter Rosin
2019-12-18 12:28 ` [PATCH v3 6/6] Revert "drm: atmel-hlcdc: enable sys_clk during initalization." Claudiu Beznea
2020-01-02 9:05 ` [PATCH v3 0/6] fixes for atmel-hlcdc Sam Ravnborg
2020-01-02 16:05 ` Lee Jones
2020-01-02 16:21 ` Sam Ravnborg
2020-01-06 19:37 ` Sam Ravnborg
2020-01-07 10:17 ` [GIT PULL] Immutable branch between MFD and DRM due for the v5.6 merge window Lee Jones
2020-01-07 18:21 ` Sam Ravnborg [this message]
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=20200107182124.GB20555@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=peda@axentia.se \
/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).