All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
	Tejun Heo <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>,
	Francis Russell <francisrussell@btopenworld.com>,
	Robert de Rooy <robert.de.rooy@gmail.com>,
	Alan Cox <alan@redhat.com>,
	video4linux@list.redhat.com, Hans Verkuil <hverkuil@xs4all.nl>,
	Robert Fitzsimons <robfitz@273k.net>
Subject: Re: [3/5] 2.6.22-rc2: known regressions
Date: Mon, 21 May 2007 07:44:04 -0300	[thread overview]
Message-ID: <1179744244.4138.47.camel@localhost> (raw)
In-Reply-To: <464F74D5.9080204@googlemail.com>

Hi Michal,

Em Dom, 2007-05-20 às 00:06 +0200, Michal Piotrowski escreveu:

> V4L
> 
> Subject    : V4L ABI breakage
> References : http://lkml.org/lkml/2007/5/14/42
> Submitter  : Robert Fitzsimons <robfitz@273k.net>
> Caused-By  : Hans Verkuil <hverkuil@xs4all.nl>
>              Mauro Carvalho Chehab <mchehab@infradead.org>
>              commit 206ebaf32795cf1582b1e2ff2ec6a560c9e986b8
> Status     : Unknown

I was traveling abroad last week, without access to my devel
environment. Hans is currently working on a definitive fix for the
issue. His schedule is to have a proper solution until next week.

For now, it is better just to revert the bad changes. I've committed a
patch on my tree for that:

http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=15ac2d293b08b6975c6ca1a80eb839d4cb0dddbf

I'm currently running some tests on my environment with the fix patches
I currently have. I should send a pull request to Linus later today.

-- 
Cheers,
Mauro


  parent reply	other threads:[~2007-05-21 13:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <464F6DC9.80805@googlemail.com>
2007-05-19 22:05 ` [2/5] 2.6.22-rc2: known regressions Michal Piotrowski
2007-05-19 22:14   ` Indan Zupancic
2007-05-19 22:17     ` Michal Piotrowski
2007-05-19 22:27   ` Stefan Richter
2007-05-19 22:37     ` Michal Piotrowski
2007-05-19 23:27   ` Maurice van der Pot
2007-05-19 22:06 ` [3/5] " Michal Piotrowski
2007-05-19 22:06 ` Michal Piotrowski
2007-05-20 10:51   ` Tejun Heo
2007-05-20 14:32     ` Alan Cox
2007-05-21 10:44   ` Mauro Carvalho Chehab [this message]
2007-05-19 22:06 ` [4/5] " Michal Piotrowski
2007-05-19 22:23   ` Stefan Richter
2007-05-19 22:23     ` Stefan Richter
2007-05-19 22:06 ` Michal Piotrowski
2007-05-19 22:06 ` [5/5] " Michal Piotrowski
2007-05-19 22:06 ` Michal Piotrowski
2007-05-19 22:06 ` Michal Piotrowski
2007-05-19 22:38   ` David Miller
2007-05-19 22:38     ` David Miller
2007-05-20  4:57     ` Stephen Hemminger
2007-05-20  4:57       ` Stephen Hemminger
2007-05-20 11:15       ` Herbert Xu

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=1179744244.4138.47.camel@localhost \
    --to=mchehab@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@redhat.com \
    --cc=francisrussell@btopenworld.com \
    --cc=htejun@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jeff@garzik.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=robert.de.rooy@gmail.com \
    --cc=robfitz@273k.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.