[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6D8AF2F@saturn3.aculab.com>
Date: Thu, 5 Jan 2012 10:41:28 -0000
From: "David Laight" <David.Laight@...LAB.COM>
To: "Joe Perches" <joe@...ches.com>,
"Kalle Valo" <kvalo@....qualcomm.com>
Cc: <linville@...driver.com>, <sfr@...b.auug.org.au>,
<netdev@...r.kernel.org>, <linux-wireless@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-next@...r.kernel.org>,
<ath6kl-devel@...lcomm.com>, <davem@...emloft.net>
Subject: RE: [PATCH 5/6] ath6kl: convert ath6kl_dbg() and ath6kl_dbg_dump() into functions
> > + va_start(args, fmt);
> > + ath6kl_printk(KERN_DEBUG, fmt, &args);
>
> Passing a va_list as an argument?
> I believe this doesn't work.
> I think you'll need to add and use:
Passing a va_list certainly does work - vprintf() etc.
What is problematical is taking the address of a va_list.
The likely problem is a 'levels of indirection' one
because, when va_list needs to be a struct (very
likely when arguments are passed in registers),
it is often declared as as array type.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists