All of lore.kernel.org
 help / color / mirror / Atom feed
From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: pr_debug
Date: Wed, 15 Mar 2017 21:40:44 +1100	[thread overview]
Message-ID: <20170315104044.GA29639@eros> (raw)
In-Reply-To: <CAJ1xhMUnAF+c=eE89SXxLtfgLAv-VubmbSPK3m8bTOQ+cMrTvA@mail.gmail.com>

On Wed, Mar 15, 2017 at 12:01:39PM +0200, Alexander Kapshuk wrote:
> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <me@tobin.cc> wrote:
> > why does calling pr_debug() with more than one argument cause a sparse
> > warning?
> >
> > drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
> >
> > sdio_io.c:70:
> > pr_debug("SDIO: Enabling device %s...\n", sdio_func_id(func));
> >
> > What can we do about this?
> >
> > thanks,
> > Tobin.
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 
> What is the version of the sources you are using?

I'm usually working of gregKH's staging tree using branch staging-next
and/or staging-testing

thanks,
Tobin.

  reply	other threads:[~2017-03-15 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  8:31 pr_debug Tobin C. Harding
2017-03-15 10:01 ` pr_debug Alexander Kapshuk
2017-03-15 10:40   ` Tobin C. Harding [this message]
2017-03-15 10:55     ` pr_debug Alexander Kapshuk
2017-03-15 11:12       ` pr_debug Bjørn Mork
2017-03-15 21:15         ` pr_debug Tobin C. Harding
2017-03-16 11:17           ` pr_debug Alexander Kapshuk
2017-03-16 12:40             ` pr_debug Tobin C. Harding
  -- strict thread matches above, loose matches on Subject: below --
2016-05-10  7:21 pr_debug Tobin Harding
2016-05-10  7:33 ` pr_debug Greg KH
2016-05-10  7:36   ` pr_debug Tobin Harding

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=20170315104044.GA29639@eros \
    --to=me@tobin.cc \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.