public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	Jonathan Cameron <jic23@cam•ac.uk>,
	linux-iio@vger•kernel.org
Subject: Re: linux-next: Tree for Mar 6 (staging/iio)
Date: Tue, 06 Mar 2012 10:51:28 -0800	[thread overview]
Message-ID: <4F565CB0.8070301@xenotime.net> (raw)
In-Reply-To: <20120306180746.25c595babf8b5072366cdbec@canb.auug.org.au>

On 03/05/2012 11:07 PM, Stephen Rothwell wrote:

> Hi all,
> 
> Changes since 20120305:


When CONFIG_DEBUG_FS is not enabled:

drivers/staging/iio/industrialio-core.c:621:11: error: 'iio_read_channel_ext_info' undeclared (first use in this function)
drivers/staging/iio/industrialio-core.c:623:11: error: 'iio_write_channel_ext_info' undeclared (first use in this function)




-- 
~Randy

  reply	other threads:[~2012-03-06 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  7:07 linux-next: Tree for Mar 6 Stephen Rothwell
2012-03-06 18:51 ` Randy Dunlap [this message]
     [not found]   ` <4F565CB0.8070301-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-03-06 19:43     ` [PATCH] staging:iio: Fix compile error without CONFIG_DEBUG_FS Lars-Peter Clausen
     [not found]       ` <1331063025-25242-1-git-send-email-lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2012-03-06 20:03         ` Randy Dunlap
2012-03-06 20:06 ` linux-next: Tree for Mar 6 (nfs) Randy Dunlap
     [not found]   ` <4F566E37.5040009-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-03-13 20:58     ` Randy Dunlap

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=4F565CB0.8070301@xenotime.net \
    --to=rdunlap@xenotime$(echo .)net \
    --cc=jic23@cam$(echo .)ac.uk \
    --cc=linux-iio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@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