From: Mike Frysinger <vapier.adi@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Lothar Wassmann <LW@karo-electronics.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Hennerich <michael.hennerich@analog.com>,
Bryan Wu <cooloney@kernel.org>,
Lothar Wassmann <lothar@ipc1.ka-ro>
Subject: Re: [PATCH] Fix compiler warnings and remove debug messages
Date: Tue, 11 Aug 2009 03:59:43 -0400 [thread overview]
Message-ID: <8bd0f97a0908110059y344071adn3656eaea3d7edddf@mail.gmail.com> (raw)
In-Reply-To: <20090811000112.GB13314@kroah.com>
On Mon, Aug 10, 2009 at 20:01, Greg KH wrote:
> On Mon, Aug 10, 2009 at 06:28:56PM +0200, Lothar Wassmann wrote:
>> This patch fixes the reported compiler warnings and removes excessive debug messages.
>> Compile tested only!
>
> I'd prefer the correct fixes for this driver. Mike, any thoughts on
> some fixes for this?
if it's simply fixing printf modifiers, then i can send out a patch for that.
the changelog simply states "the reported compiler warnings" ... what
exactly must i do to reproduce these ?
-mike
next prev parent reply other threads:[~2009-08-11 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 9:36 linux-next: usb tree build warnings Stephen Rothwell
2009-08-10 13:54 ` diff --git a/drivers/usb/host/isp1362-hcd.c b/drivers/usb/host/isp1362-hcd.c Lothar Wassmann
[not found] ` <<20090810193653.f228cf06.sfr@canb.auug.org.au>
2009-08-10 16:28 ` [PATCH] Fix compiler warnings and remove debug messages Lothar Wassmann
2009-08-11 0:01 ` Greg KH
2009-08-11 7:59 ` Mike Frysinger [this message]
2009-08-11 8:31 ` Stephen Rothwell
2009-08-11 0:00 ` linux-next: usb tree build warnings Greg KH
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=8bd0f97a0908110059y344071adn3656eaea3d7edddf@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=LW@karo-electronics.de \
--cc=cooloney@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lothar@ipc1.ka-ro \
--cc=michael.hennerich@analog.com \
--cc=sfr@canb.auug.org.au \
/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).