From: Simon Budig <simon.budig@kernelconcepts.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: linux-next: Tree for Aug 14 (drivers/input/touchscreen/edt-ft5x06.c)
Date: Wed, 15 Aug 2012 01:15:58 +0200 [thread overview]
Message-ID: <502ADC2E.5070003@kernelconcepts.de> (raw)
In-Reply-To: <502A9200.1020606@xenotime.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/14/2012 07:59 PM, Randy Dunlap wrote:
> 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'
Yeah, unfortunate oversight on my part.
Guenter Roeck provided a patch for this issue which looks good to me.
(Aug 7th, linux-input mailinglist)
Dmitry: Can you upstream this? Is there any action required on my part?
Thanks,
Simon
- --
Simon Budig kernel concepts GmbH
simon.budig@kernelconcepts.de Sieghuetter Hauptweg 48
+49-271-771091-17 D-57072 Siegen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAq3C4ACgkQO2O/RXesiHAofACgsPG5EcF3fn0me1STCIK5nYwm
4QkAoL+Q30zA0NLNbUSPJIRt6CmR4o91
=y99v
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-08-14 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 3:55 linux-next: Tree for Aug 14 Stephen Rothwell
2012-08-14 17:54 ` linux-next: Tree for Aug 14 (media/dvb/dvb-usb-v2/anysee) Randy Dunlap
2012-08-14 18:40 ` Antti Palosaari
2012-08-14 17:59 ` linux-next: Tree for Aug 14 (drivers/input/touchscreen/edt-ft5x06.c) Randy Dunlap
2012-08-14 23:15 ` Simon Budig [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=502ADC2E.5070003@kernelconcepts.de \
--to=simon.budig@kernelconcepts.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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.