public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Michał Mirosław" <mirq-linux@rere•qmqm.pl>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Randy Dunlap <randy.dunlap@oracle•com>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	Pierre Ossman <pierre@ossman•eu>
Subject: Re: [PATCH -next] mmc: cb710 cleanups
Date: Sat, 6 Jun 2009 11:59:26 +0200	[thread overview]
Message-ID: <20090606095926.GA5455@rere.qmqm.pl> (raw)
In-Reply-To: <4A295DD9.2050301@oracle.com>

Hello,

On Fri, Jun 05, 2009 at 11:03:05AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle•com>
> 
> - don't define DEBUG, just use CONFIG_CB710_DEBUG or CONFIG_MMC_DEBUG
> - fix printk format warnings
> 
> In file included from drivers/mmc/host/cb710-mmc.h:13,
>                  from drivers/mmc/host/cb710-mmc.c:15:
> include/linux/cb710.h:14:1: warning: "DEBUG" redefined
> <command-line>: warning: this is the location of the previous definition
> 
> drivers/mmc/host/cb710-mmc.c:222: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
> drivers/mmc/host/cb710-mmc.c:222: warning: format '%d' expects type 'int', but argument 6 has type 'size_t'

Fixes for these warnings are already queued in Pierre's mailbox. 
Should I Cc: linux-next from now on since the base patch went to linux-next?

Best Regards,
Michał Mirosław

      reply	other threads:[~2009-06-06  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  6:41 linux-next: Tree for June 5 Stephen Rothwell
2009-06-05 18:03 ` [PATCH -next] mmc: cb710 cleanups Randy Dunlap
2009-06-06  9:59   ` Michał Mirosław [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=20090606095926.GA5455@rere.qmqm.pl \
    --to=mirq-linux@rere$(echo .)qmqm.pl \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=pierre@ossman$(echo .)eu \
    --cc=randy.dunlap@oracle$(echo .)com \
    --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