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>,
Simon Budig <simon.budig@kernelconcepts.de>,
linux-input@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 14 (drivers/input/touchscreen/edt-ft5x06.c)
Date: Tue, 14 Aug 2012 10:59:28 -0700 [thread overview]
Message-ID: <502A9200.1020606@xenotime.net> (raw)
In-Reply-To: <20120814135506.b6b86e3c8cb9da1eefb7bbd6@canb.auug.org.au>
On 08/13/2012 08:55 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120813:
>
on x86_64, when CONFIG_DEBUG_FS is not enabled:
drivers/input/touchscreen/edt-ft5x06.c: In function 'edt_ft5x06_ts_remove':
drivers/input/touchscreen/edt-ft5x06.c:846:14: error: 'struct edt_ft5x06_ts_data' has no member named 'raw_buffer'
--
~Randy
next parent reply other threads:[~2012-08-14 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120814135506.b6b86e3c8cb9da1eefb7bbd6@canb.auug.org.au>
2012-08-14 17:59 ` Randy Dunlap [this message]
2012-08-14 23:15 ` linux-next: Tree for Aug 14 (drivers/input/touchscreen/edt-ft5x06.c) Simon Budig
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=502A9200.1020606@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simon.budig@kernelconcepts.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).