From: Harvey Harrison <harvey.harrison@gmail.com>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
"v4l-dvb-maintainer@linuxtv.org" <v4l-dvb-maintainer@linuxtv.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCTION__ occurences
Date: Mon, 03 Mar 2008 19:29:54 -0800 [thread overview]
Message-ID: <1204601394.22933.99.camel@brick> (raw)
In-Reply-To: <37219a840803031928l79395c78ka64192f4a9f61744@mail.gmail.com>
On Mon, 2008-03-03 at 22:28 -0500, 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.
>
> Other than that, I'm fine with this change if that's what we're doing
> across the rest of the kernel... Would just be easier to deal with if
> it could be further broken down by subdirectory.
No worries on my part, point me at what tree you'd like it against, and
how you'd like it broken up. Or just give me a shout when it is most
convenient to send an update.
Harvey
next prev parent reply other threads:[~2008-03-04 3:30 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 [this message]
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 ` [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCT ION__ occurences mkrufky
2008-04-04 15:09 ` 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=1204601394.22933.99.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mkrufky@linuxtv.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