> Given that the compat module is shared, and a quite a bit of other
> code / style is shared, and I'd love to see us start to formalize
> documenting collateral evolutions on the kernel in one place I'd like
> to propose to you merging this into compat-wirless and we then rename
> the project to c
> Given that the compat module is shared, and a quite a bit of other
> code / style is shared, and I'd love to see us start to formalize
> documenting collateral evolutions on the kernel in one place I'd like
> to propose to you merging this into compat-wirless and we then rename
> the project to c
On Wed, Jun 27, 2012 at 3:27 PM, Ozan Çağlayan wrote:
> Hi,
>
> I'm maintaining a compat-drm tree (based on compat.git) as part of my
> GSoC project with Linux Foundation, under the mentorship of Luis R.
> Rodriguez.
>
> The aim of the tree is to offer the latest DRM stuff to people stuck
> with o
On Wed, Jun 27, 2012 at 3:27 PM, Ozan ?a?layan wrote:
> Hi,
>
> I'm maintaining a compat-drm tree (based on compat.git) as part of my
> GSoC project with Linux Foundation, under the mentorship of Luis R.
> Rodriguez.
>
> The aim of the tree is to offer the latest DRM stuff to people stuck
> with o
Hi,
I'm maintaining a compat-drm tree (based on compat.git) as part of my
GSoC project with Linux Foundation, under the mentorship of Luis R.
Rodriguez.
The aim of the tree is to offer the latest DRM stuff to people stuck
with older kernels (Currently all of the popular and maintained drm
drivers
Hi,
I'm maintaining a compat-drm tree (based on compat.git) as part of my
GSoC project with Linux Foundation, under the mentorship of Luis R.
Rodriguez.
The aim of the tree is to offer the latest DRM stuff to people stuck
with older kernels (Currently all of the popular and maintained drm
drivers
