LKML Archive on
help / color / mirror / Atom feed
From: Patrick Boettcher <>
To: Mauro Carvalho Chehab <>
Cc: Linux Kernel Mailing List <>
Subject: Re: [GIT PULL for 2.6.38-rc2] V4L/DVB patches
Date: Mon, 31 Jan 2011 21:55:59 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Mauro,

On Friday 21 January 2011 14:17:09 Mauro Carvalho Chehab wrote:
> Linus,
> Em 20-01-2011 15:01, Mauro Carvalho Chehab escreveu:
> > Hi Linus,
> > 
> > Those are some changes that I tried to prepare to send you during the
> > merge window, but, unfortunately, the new videobuf2 driver took me a
> > longer time to review/test than I originally expected.
> > 
> > Please pull from:
> >   ssh://
> >   v4l_for_linus
> Please, don't pull yet. There are some changesets that have some
> weird stuff, like this:
> diff --git a/drivers/staging/vme/bridges/Module.symvers
> b/drivers/staging/vme/bridges/Module.symvers deleted file mode 100644
> index e69de29..0000000
> I have no idea why those things appeared, as I never handled any patch
> that touched inside drivers/staging/vme. I need to further investigate
> the entire patchset and see if other weird stuff happened there.
> I'll send you another pull request after fixing those things.

Do you think those changesets will make it into 2.6.38 at some point? I'm 
asking because this is where the technisat-driver is currently residing on his 
way into the kernel.  I understand that there is a problem in this branch, but 
still I'd like to see the technisat-usb2 being merged.

I'm getting a little bit desperate. :-(

Can I do something to help?

best regards,
Patrick Boettcher - KernelLabs

  reply	other threads:[~2011-01-31 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 17:01 Mauro Carvalho Chehab
2011-01-21 13:17 ` Mauro Carvalho Chehab
2011-01-31 20:55   ` Patrick Boettcher [this message]
2011-02-02 12:55     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [GIT PULL for 2.6.38-rc2] V4L/DVB patches' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).