All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozancag@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: lf_driver_backport@lists.linux-foundation.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Lf_driver_backport] [ANN] compat-drm tree
Date: Fri, 29 Jun 2012 13:35:58 +0300	[thread overview]
Message-ID: <CAFub=KT1ey_5E3Lvg0a0x3BsAjXs4MaS_MzWecFByNNTQNEECg@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6VvKp6Nq1K4in__HkCY555F9A2FpGqdARVGh8gMu2h3jg@mail.gmail.com>

> 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 compat-drivers, with you maintaining the drm
> components. This also gives us an already established quick outlet for
> redistribution as well. What do you think?

Okay, this makes sense.

>
> Some comments:
>
> In the patches/ directory if you can add a description on the top of
> each patch explaining *why* that collateral evolution was not
> backportable through compat it would help. It sets the standard for
> others introducing similar types of patches.

Ah I forgot about this :)

>
> For patches/00-vga_switcheroo_client_ops.patch:
>
> I wonder if you may be able to get rid of this patch. The attached
> patch is an RFC patch for compat.git which explains how I'm thinking
> this may be possible, I don't have time to test it but let me know
> what you think.

Okay will test and try to drop the patch as well.

Thanks :)

-- 
Ozan Çağlayan
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2012-06-29 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 22:27 [ANN] compat-drm tree Ozan Çağlayan
2012-06-28 19:38 ` [Lf_driver_backport] " Luis R. Rodriguez
2012-06-29 10:35   ` Ozan Çağlayan [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='CAFub=KT1ey_5E3Lvg0a0x3BsAjXs4MaS_MzWecFByNNTQNEECg@mail.gmail.com' \
    --to=ozancag@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lf_driver_backport@lists.linux-foundation.org \
    --cc=mcgrof@frijolero.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.