From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933179AbZJaTKf (ORCPT ); Sat, 31 Oct 2009 15:10:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933134AbZJaTKf (ORCPT ); Sat, 31 Oct 2009 15:10:35 -0400 Received: from perceval.irobotique.be ([92.243.18.41]:33061 "EHLO perceval.irobotique.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932977AbZJaTKe (ORCPT ); Sat, 31 Oct 2009 15:10:34 -0400 From: Laurent Pinchart To: Mauro Carvalho Chehab Subject: Re: [PATCH 5/8] drivers/media/video/uvc: Use %pUl to print UUIDs Date: Sat, 31 Oct 2009 20:10:39 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.31.1; KDE/4.3.2; x86_64; ; ) Cc: Joe Perches , linux-kernel@vger.kernel.org, Andrew Morton , linux-media@vger.kernel.org References: <1254890742-28245-1-git-send-email-joe@perches.com> <200910120034.58943.laurent.pinchart@ideasonboard.com> <20091031070701.4ccf27d5@caramujo.chehab.org> In-Reply-To: <20091031070701.4ccf27d5@caramujo.chehab.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910312010.39785.laurent.pinchart@ideasonboard.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 31 October 2009 10:07:01 Mauro Carvalho Chehab wrote: > Hi Laurent, > > Em Mon, 12 Oct 2009 00:34:58 +0200 > > Laurent Pinchart escreveu: > > As this will go through the linuxtv v4l-dvb tree, I'll have to add > > backward compatibility code (that will not make it to mainline). If > > that's ok with you it will be easier for me to test and apply that part > > of the patch through my tree once the vsprintf extension gets in. > > I'm assuming that those printk patches from Joe to uvc will go via your > tree, so please submit a pull request when they'll be ready for upstream. I'll submit the pull request as soon as the printk core patch hits upstream. The change will break the driver when used with older versions (it will compile, load and run, but will print broken messages), and compat.h compatibility magic will not be possible. As the messages are purely informational, I'm pondering not even keeping #ifdef compatibility. Any thought on that ? -- Regards, Laurent Pinchart