mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Joe Perches <joe@perches.com>,
	Douglas Schilling Landgraf <dougsland@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] drivers/media/video/uvc: Use %pUl to print UUIDs
Date: Wed, 3 Feb 2010 02:18:20 +0100	[thread overview]
Message-ID: <201002030218.20251.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <1265133043.1945.13.camel@Joe-Laptop.home>

On Tuesday 02 February 2010 18:50:43 Joe Perches wrote:
> On Tue, 2010-02-02 at 13:23 -0200, Mauro Carvalho Chehab wrote:
> > I'm reviewing all patches marked as under review at Patchwork and I
> > noticed that this one were never applied, nor I found any nack at
> > linux-media ML.
> >
> > What's the status for it?
> 
> Laurent wanted it withdrawn so he could fix some
> backward compatibility thing he wanted.
> 
> http://lkml.org/lkml/2009/11/4/216
> 
> Nothing's happened since as far as I know.

There's a patch in my git tree, I'll send a pull request tomorrow. I had 
actually prepared a -hg compat patch as well, but the switch to git changed 
the workflow.

Douglas, will you handle the -hg compat "automatically" ? The code will 
compile on older kernels without a warning, but it will still require #ifdef's 
to run correctly on older kernels. Is there a standard way to notify you about 
that during patches submission ?

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2010-02-03  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1255471594.18975.79.camel@Joe-Laptop.home>
     [not found] ` <20091013151652.5d2a49b7.akpm@linux-foundation.org>
2009-10-13 23:35   ` Joe Perches
2010-02-02 15:23     ` Mauro Carvalho Chehab
2010-02-02 17:50       ` Joe Perches
2010-02-03  1:18         ` Laurent Pinchart [this message]

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=201002030218.20251.laurent.pinchart@ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dougsland@gmail.com \
    --cc=joe@perches.com \
    --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

all inboxes | Powered by JetHome®