From: mkrufky@linuxtv.org
To: harvey.harrison@gmail.com
Cc: abraham.manu@gmail.com, v4l-dvb-maintainer@linuxtv.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mchehab@infradead.org
Subject: Re: [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCT ION__ occurences
Date: Thu, 3 Apr 2008 14:58:55 -0500 [thread overview]
Message-ID: <47F536FF.8060105@linuxtv.org> (raw)
In-Reply-To: <1204613661.22933.110.camel@brick>
Harvey Harrison wrote:
> On Tue, 2008-03-04 at 01:38 -0500, Michael Krufky wrote:
>
>> Manu Abraham wrote:
>>
>>> Michael Krufky wrote:
>>>
>>>> On Mon, Mar 3, 2008 at 7:03 PM, Harvey Harrison
>>>> <harvey.harrison@gmail.com> wrote:
>>>>
>>>>> __FUNCTION__ is gcc-specific, use __func__
>>>>>
>>>>> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
>>>>> 162 files changed, 892 insertions(+), 892 deletions(-)
>>>>>
>>>> If we apply this, can it be broken down into several smaller patches?
>>>> I am in the midst of a large overhaul of the tuning subsystem, and if
>>>> this all gets applied at once, it will wreck havoc on my pending
>>>> changesets.
>>>>
>>> Please make sure your changes don't conflict with the multiproto tree
>>> changes.
>>>
>>> Regards,
>>> Manu
>>>
>> Manu,
>>
>> Does that mean that you plan to merge multiproto soon? If that's the
>> case, then we'd be better off if you give Harvey an "exclude list" of
>> files he should stay away from. He can regenerate patches to those
>> files after multiproto is merged.
>>
>>
>
> Or just apply it after both of you have merged and ignore any conflicts,
> I can come back to it at a later time (2.6.26-rc1 maybe?).
Harvey,
The greater portion of my refactoring changes have been merged. As far
as I am concerned, you should feel free to send in cleanup changesets now.
Manu,
We can't expect Harvey to avoid conflicts with multiproto -- do you have
any plans to ACTUALLY merge these changes? You've been saying "any day
now" for the past two years.
If you plan to merge multiproto for 2.6.26, then, IMHO, now is the
time. Otherwise, it's safe for Harvey to do his cleanups.
Harvey,
If you decide to move forward with these cleanups now, please keep the
previous discussion in mind -- please generate the changesets against
the v4l-dvb master repository, hosted on linuxtv.org, and please
separate the changesets by each level of the directory tree hierarchy.
Regards,
Mike Krufky
next prev parent reply other threads:[~2008-04-03 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:03 [PATCH] media: replace remaining __FUNCTION__ occurences Harvey Harrison
2008-03-04 3:28 ` [v4l-dvb-maintainer] " Michael Krufky
2008-03-04 3:29 ` Harvey Harrison
2008-03-04 3:47 ` Michael Krufky
2008-03-04 5:17 ` Manu Abraham
2008-03-04 6:38 ` Michael Krufky
2008-03-04 6:54 ` Harvey Harrison
2008-04-03 19:58 ` mkrufky [this message]
2008-04-04 15:09 ` [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCT ION__ occurences Michael Krufky
2008-04-09 17:00 ` Michael Krufky
2008-04-09 18:11 ` Oliver Endriss
2008-04-09 18:30 ` Harvey Harrison
2008-04-09 18:58 ` Mauro Carvalho Chehab
2008-04-09 19:05 ` mkrufky
2008-03-04 10:33 ` [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCTION__ occurences Manu Abraham
2008-03-04 13:50 ` Mauro Carvalho Chehab
2008-03-04 20:19 ` Manu Abraham
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=47F536FF.8060105@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=abraham.manu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.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;
as well as URLs for NNTP newsgroup(s).