public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-dvb-maintainer@linuxtv.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 08:38:14 -0700	[thread overview]
Message-ID: <20080728083814.ea480697.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080728122518.77cea66e@gaivota>

On Mon, 28 Jul 2008 12:25:18 -0300 Mauro Carvalho Chehab wrote:

> 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

Thanks for the info.  I'll wait for tomorrow's linux-next.

(having to git up to 200 or so git trees does not scale IMO)


---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/

  reply	other threads:[~2008-07-28 15:40 UTC|newest]

Thread overview: 9+ 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
2008-07-28  3:42 ` Randy Dunlap
2008-07-28  7:08   ` Mauro Carvalho Chehab
2008-07-28 15:18     ` Randy Dunlap
2008-07-28 15:25       ` Mauro Carvalho Chehab
2008-07-28 15:38         ` Randy Dunlap [this message]
2008-07-28 18:39         ` [PATCH] v4l: fix kernel-doc warning, function name, and docbook filename Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2008-07-20 13:59 [GIT PATCHES for 2.6.27] V4L/DVB updates 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=20080728083814.ea480697.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --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