mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@kernellabs.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media <linux-media@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PULL] http://kernellabs.com/hg/~mkrufky/sms1xxx
Date: Sun, 30 Aug 2009 08:53:35 -0400	[thread overview]
Message-ID: <303a8ee30908300553s6d81a2cdn43145de51298afd5@mail.gmail.com> (raw)
In-Reply-To: <37219a840908241332w2e2d45d8kd6406de3e60d1317@mail.gmail.com>

Mauro,

On Mon, Aug 24, 2009 at 4:32 PM, Michael Krufky<mkrufky@kernellabs.com> wrote:
> Mauro,
>
> Would you please send the final GPIO fix to Linus to fix the
> regression on the Hauppauge devices.  2.6.31 is in -rc7 now, and I
> would hate for this regression to not yet be solved before the kernel
> is released.
>
> I apologize for nagging -- I just prefer for fixes to be merged
> upstream *before* a kernel release.
>
> Thank you.
>
> Just as a reminder, the changeset that is still waiting for upstream merge is:
>
> *       sms1xxx: restore GPIO functionality for all Hauppauge devices

Just another reminder -- this is cutting it very close now.

I repeat, that this is a feature that worked in previous kernels but
is broken in 2.6.31.

I feel very concerned, considering that I posted a regression fix over
six weeks ago and it still has not made it into Linus' kernel tree.

I understand that you are a busy man -- Would it be easier for you if
I sent this patch to Linus, myself?

Please advise.

Thank you for your time.

Regards,

Michael Krufky

       reply	other threads:[~2009-08-30 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090730200714.5a7ab8a6@pedra.chehab.org>
     [not found] ` <37219a840907310825n51d5a6bar79ea1f31dd889327@mail.gmail.com>
     [not found]   ` <20090801014053.7f53da83@pedra.chehab.org>
     [not found]     ` <303a8ee30908011103n3c12258icd2bfd1305b419d3@mail.gmail.com>
     [not found]       ` <20090811140128.211d4d11@caramujo.chehab.org>
     [not found]         ` <37219a840908111457o4b6abc64n52291f044b56782d@mail.gmail.com>
     [not found]           ` <37219a840908241332w2e2d45d8kd6406de3e60d1317@mail.gmail.com>
2009-08-30 12:53             ` Michael Krufky [this message]
2009-08-30 22:13               ` Mauro Carvalho Chehab
2009-08-31 11:03                 ` Michael Krufky
2009-09-01 13:47                   ` Mauro Carvalho Chehab
2009-09-01 15:03                     ` Michael Krufky
2009-09-01 19:36                       ` 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=303a8ee30908300553s6d81a2cdn43145de51298afd5@mail.gmail.com \
    --to=mkrufky@kernellabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@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

all inboxes | Powered by JetHome®