From: Douglas Schilling Landgraf <dougsland@gmail.com>
To: Andy Walls <awalls@radix.net>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>, linux-media@vger.kernel.org
Subject: Re: Fix for breakage caused by kfifo backport
Date: Fri, 15 Jan 2010 10:59:27 -0200 [thread overview]
Message-ID: <4B5066AF.9020901@gmail.com> (raw)
In-Reply-To: <1263556855.3059.10.camel@palomino.walls.org>
Hello Andy,
On 01/15/2010 10:00 AM, Andy Walls wrote:
> Mauro,
>
> At
>
> http://linuxtv.org/hg/~awalls/cx23885-ir2
>
> I have a change checked in to fix the v4l-dvb compilation breakage for
> kernels less than 2.6.33 cause by the kfifo API change. I have fixed
> both the cx23885 and meye driver so they compile again for older
> kernels.
>
> All the changes in this repo are OK to PULL as is, even though I haven't
> finished all the changes for the TeVii S470 IR (I was planning on a
> PULL request late this evening EST). You can also just cherry pick the
> one that fixes the kfifo problem if you want.
>
> [I was unaware of the timing of the backport, but since it was stopping
> me from working, I fixed it as I thought appropriate.
Ouch, I was expecting to send the pull request for these changes before.
I have created the exactly same patches. Anyway, good that we have these
backports done.
> Please feel free
> to contact me on any backport changes that have my fingerprints all over
> it, with which you would like help. I'd like to help minimize the
> impact to users, testers, and developers, who may not have the bleeding
> edge kernel - or at least the impact to me ;) ]
>
>
Cheers,
Douglas
next prev parent reply other threads:[~2010-01-15 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 12:00 Fix for breakage caused by kfifo backport Andy Walls
2010-01-15 12:59 ` Douglas Schilling Landgraf [this message]
2010-01-15 19:47 ` Mauro Carvalho Chehab
2010-01-15 22:27 ` Andy Walls
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=4B5066AF.9020901@gmail.com \
--to=dougsland@gmail.com \
--cc=awalls@radix.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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