public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle•com>
To: David Vrabel <david.vrabel@csr•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	gregkh@suse•de, linux-next@vger•kernel.org,
	LKML <linux-kernel@vger•kernel.org>,
	lud <linux-usb@vger•kernel.org>
Subject: Re: [PATCH] whci: fix type and format warnings
Date: Tue, 13 Oct 2009 11:07:34 -0700	[thread overview]
Message-ID: <20091013110734.56b0e027.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4AD4BE19.8040005@csr.com>

On Tue, 13 Oct 2009 18:51:21 +0100 David Vrabel wrote:

> Randy Dunlap wrote:
> > From: Randy Dunlap <randy.dunlap@oracle•com>
> > 
> > Fix format and type warnings in whci driver:
> 
> I'd prefer this fixed differently.  Those debug messages were left in by
> mistake.  Randy, you want to respin this or shall I?

You can do it.

Thanks.

---
~Randy

      reply	other threads:[~2009-10-13 18:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13  5:23 linux-next: Tree for October 13 Stephen Rothwell
2009-10-13 10:06 ` [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault with !CONFIG_S390_EXEC_PROTECT Kamalesh Babulal
2009-10-13 10:33   ` Martin Schwidefsky
2009-10-13 10:57     ` Kamalesh Babulal
2009-10-13 16:28 ` [BUILD_FAILURE] next-20091013 s390x - build breaks SCLP VT220 terminal driver Kamalesh Babulal
2009-10-14  9:02   ` Martin Schwidefsky
2009-10-14 10:45   ` Martin Schwidefsky
2009-10-14 16:02     ` Kamalesh Babulal
2009-10-13 17:00 ` [PATCH] wan: pci200syn needs capability.h Randy Dunlap
2009-10-13 17:19   ` Krzysztof Halasa
2009-10-13 17:01 ` [PATCH] whci: fix type and format warnings Randy Dunlap
     [not found]   ` <20091013100128.0f06d67c.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-10-13 17:51     ` David Vrabel
2009-10-13 18:07       ` Randy Dunlap [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=20091013110734.56b0e027.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=david.vrabel@csr$(echo .)com \
    --cc=gregkh@suse$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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