dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jindal, Sonika" <sonika.jindal@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/6] drm: Renaming DP training vswing/pre-emph defines
Date: Wed, 06 Aug 2014 11:01:52 +0530	[thread overview]
Message-ID: <53E1BDC8.4030206@intel.com> (raw)
In-Reply-To: <CAKMK7uGMQk-b1WkAWvH+MNOEPsAnrTZKAzws2O9apx2dxrLhuQ@mail.gmail.com>



On 8/5/2014 6:00 PM, Daniel Vetter wrote:
> On Tue, Aug 5, 2014 at 1:33 PM, Jindal, Sonika <sonika.jindal@intel.com> wrote:
>>
>>
>> On 8/5/2014 4:45 PM, Daniel Vetter wrote:
>>>
>>> On Tue, Aug 05, 2014 at 04:38:17PM +0530, sonika.jindal@intel.com wrote:
>>>>
>>>> From: Sonika Jindal <sonika.jindal@intel.com>
>>>>
>>>> Renaming defines to have levels instead of nominal values.
>>>>
>>>> Signed-off-by: Sonika Jindal <sonika.jindal@intel.com>
>>>
>>>
>>> You can't split up patches like this since this will break compilation.
>>> For larger stuff (and imo this is right above the cutoff) you first need
>>> to add the new functions/defines, then convert everyone over. And only
>>> when all the drivers are converted can we apply the patch to remove the
>>> old functions/defines.
>>> -Daniel
>>>
>> Got your concern. So, I will repost the first patch keeping both the defines
>> and an additional last patch for removing the extra defines.
>
> Yeah. Btw for the actual replacement I highly recommend to do it with
> a semantic patch and cocci. There's unfortunately not a hole lot of
> good documentation around, but we recently started and it helps a lot
> with regenerating patches (e.g. for newly merged drm drivers) and
> avoiding mistakes for manual conversions. If we do a cocci patch we
> put it into the commit message, grep for @@.
> -Daniel
>
I need to find out about cocci. Can we go ahead with this patch series only?
-Sonika

  reply	other threads:[~2014-08-06  5:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 11:08 [PATCH 0/6] Rename DP training vswing/pre-emph defines sonika.jindal
2014-08-05 11:08 ` [PATCH 1/6] drm: Renaming " sonika.jindal
2014-08-05 11:15   ` Daniel Vetter
2014-08-05 11:33     ` Jindal, Sonika
2014-08-05 12:30       ` Daniel Vetter
2014-08-06  5:31         ` Jindal, Sonika [this message]
2014-08-06  2:01   ` Jingoo Han
2014-08-05 11:08 ` [PATCH 2/6] drm/i915: " sonika.jindal
2014-08-05 11:08 ` [PATCH 3/6] drm/exynos: " sonika.jindal
2014-08-05 11:08 ` [PATCH 4/6] drm/radeon: " sonika.jindal
2014-08-05 11:08 ` [PATCH 5/6] drm/gma500: " sonika.jindal
2014-08-05 11:08 ` [PATCH 6/6] drm/tegra: " sonika.jindal
2014-08-07 10:13 ` [PATCH 0/6] Rename " Damien Lespiau

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=53E1BDC8.4030206@intel.com \
    --to=sonika.jindal@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox