From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-dvb-maintainer@linuxtv.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCHES for 2.6.27] V4L/DVB updates
Date: Mon, 28 Jul 2008 12:25:18 -0300 [thread overview]
Message-ID: <20080728122518.77cea66e@gaivota> (raw)
In-Reply-To: <20080728081813.423ac50c.randy.dunlap@oracle.com>
On Mon, 28 Jul 2008 08:18:13 -0700
Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Mon, 28 Jul 2008 03:08:27 -0400 (EDT) Mauro Carvalho Chehab wrote:
>
> > Hi Randy,
> >
> > > I'd really like to get this patch that I mailed to you 2008-July-21 merged...
> >
> > Your patch looks OK to me. However, this function were moved to
> > v4l2-dev.c, by the V4L core changes (the changes broke videodev into two
> > different files, and did some improvements there).
> >
> > Do you mind to rebase your patch?
>
> What tree contains v4l2-dev.c?
> It's not in today's linux-next. Shouldn't it be, or is it for after 2.6.27?
I've changed my procedures to generate my trees, to avoid needing to rebase all
branches (the idea is to have just for_linus rebased).
Due to that change, only yesterday I fixed the updates for linux-next (also,
I've applied the pending patches only yesterday, including the ones that
touched on V4L core). Probably, that's the reason why linux-next is not
updated. Let's see if tomorrow's version will be ok.
At the meantime, you can use my -git tree:
http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=summary
Cheers,
Mauro.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-07-28 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 1:41 [GIT PATCHES for 2.6.27] V4L/DVB updates Mauro Carvalho Chehab
2008-07-28 1:50 ` [v4l-dvb-maintainer] " Markus Rechberger
[not found] ` <20080727204256.bba5eaf6.randy.dunlap@oracle.com>
2008-07-28 7:08 ` Mauro Carvalho Chehab
[not found] ` <20080728081813.423ac50c.randy.dunlap@oracle.com>
2008-07-28 15:25 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-20 13:59 Mauro Carvalho Chehab
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=20080728122518.77cea66e@gaivota \
--to=mchehab@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=video4linux-list@redhat.com \
/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