linux-kernel - Re: [PATCH 4/3] drm: arm-hdlcd: add explictit DRM dependency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160111141400.GJ13633@e106497-lin.cambridge.arm.com>
Date:	Mon, 11 Jan 2016 14:14:00 +0000
From:	Liviu Dudau <liviu.dudau@....com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Thierry Reding <thierry.reding@...il.com>,
	David Airlie <airlied@...ux.ie>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/3] drm: arm-hdlcd: add explictit DRM dependency

On Mon, Jan 11, 2016 at 02:49:10PM +0100, Arnd Bergmann wrote:
> On Monday 11 January 2016 12:26:44 Liviu Dudau wrote:
> > > If so, just fold my fixes into your patches when you rebase.
> > 
> > OK, will do. Repeating the question on another thread: are you OK with me carrying
> > the Juno .dts changes through drm-next for HDLCD and you picking up Robin Murphy's
> > patch? AFAIK those are the only changes at the moment until Sudeep re-submits the
> > Juno r2 dts changes.
> 
> Is there a strong reason for it? Usually the preferred way is to merge all
> dts changes through arm-soc, but we can make exceptions if necessary.

No strong reason, just packing the series in a logical way. I'm happy to split the
pull requests. Will send the dts changes to you then.

Best regards,
Liviu

> 
> 	Arnd
> 

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯