[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37219a840803031947t31c3b302iaa00526f3c0a82c8@mail.gmail.com>
Date: Mon, 3 Mar 2008 22:47:01 -0500
From: "Michael Krufky" <mkrufky@...uxtv.org>
To: "Harvey Harrison" <harvey.harrison@...il.com>
Cc: "Mauro Carvalho Chehab" <mchehab@...radead.org>,
"v4l-dvb-maintainer@...uxtv.org" <v4l-dvb-maintainer@...uxtv.org>,
LKML <linux-kernel@...r.kernel.org>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCTION__ occurences
On Mon, Mar 3, 2008 at 10:29 PM, Harvey Harrison
<harvey.harrison@...il.com> wrote:
>
> 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@...il.com> wrote:
> > > __FUNCTION__ is gcc-specific, use __func__
> > >
> > > Signed-off-by: Harvey Harrison <harvey.harrison@...il.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.
OK... The v4l-dvb development tree is located on linuxtv.org...
Patches should be generated against the master repository, located
here:
http://linuxtv.org/hg/v4l-dvb
As far as breaking up the patch, it would be most convenient for me if
you could break it down such that it is separated by subdirectory, ie:
media/video/cx88/*.[ch]
media/video/saa7134/*.[ch]
media/video/*.[ch]
media/dvb/flexcop/*.[ch]
media/dvb/frontends/*.[ch]
etc... you get the idea --
There's no need to blast all of those patches onto the mailing lists
-- if you put them all into a tar.gz and email them to me privately,
then I'll push them into my mercurial tree and ask Mauro to merge them
into the master devel branch... They'll most likely end up going to
2.6.26
Having them broken down by directory will allow me to merge them in
without conflicting with other pending changesets.
Regards,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists