From: "Gregor Jasny" <gjasny@googlemail.com>
To: "Mauro Carvalho Chehab" <mchehab@infradead.org>
Cc: "Gregor Jasny" <jasny@vidsoft.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vivi driver works only as first device
Date: Sun, 6 Jan 2008 23:47:19 +0100 [thread overview]
Message-ID: <9d2cd630801061447w33478ad3p4eb24640e7f8784@mail.gmail.com> (raw)
In-Reply-To: <1197270531.5168.5.camel@gaivota>
On Dec 10, 2007 8:08 AM, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> Thanks for the report. Instead of applying your patch, I decided to
> better analyze the issue, fixing it with the proper solution. The issue
> is that vivi_register changes iminor, but this change were not properly
> returned to the driver.
Any chance to push this into 2.6.24?
Gregor
next prev parent reply other threads:[~2008-01-06 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071203225610.GS17496@vidsoft.de>
2007-12-06 22:06 ` [PATCH] vivi driver works only as first device Gregor Jasny
2007-12-10 7:08 ` Mauro Carvalho Chehab
2008-01-06 22:47 ` Gregor Jasny [this message]
2008-01-07 9:46 ` 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=9d2cd630801061447w33478ad3p4eb24640e7f8784@mail.gmail.com \
--to=gjasny@googlemail.com \
--cc=jasny@vidsoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).