From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Gerecke <killertofu@gmail.com>,
Lan Tianyu <tianyu.lan@intel.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: build failure after merge of the input tree
Date: Thu, 4 Oct 2012 23:12:36 -0700 [thread overview]
Message-ID: <20121005061236.GA11112@core.coreip.homeip.net> (raw)
In-Reply-To: <20121005114712.02361628ba297ef695d54876@canb.auug.org.au>
Hi Stephen,
On Fri, Oct 05, 2012 at 11:47:12AM +1000, Stephen Rothwell wrote:
> Hi Dmitry,
>
> After merging the input tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/input/tablet/wacom_sys.c: In function 'wacom_get_sibling':
> drivers/input/tablet/wacom_sys.c:643:23: error: 'struct usb_device' has no member named 'children'
>
> Caused by commit 316f18bba311 ("Input: wacom - handle split-sensor
> devices with internal hubs") interacting with commit ff823c79a5c3 ("usb:
> move children to struct usb_port") that is now in Linus' tree.
>
> I have used the input tree from next-20121004 for today.
Sorry about this. I pulled the offending patch and another one depending
on it out of my next branch pending my next pull from mainline.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-10-05 6:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 1:47 linux-next: build failure after merge of the input tree Stephen Rothwell
2012-10-05 6:12 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-02 3:47 Stephen Rothwell
2025-07-02 4:01 ` Dmitry Torokhov
2022-10-24 23:00 Stephen Rothwell
2022-10-25 5:02 ` Dmitry Torokhov
2022-08-17 0:00 Stephen Rothwell
2022-08-17 0:07 ` Stephen Rothwell
2022-08-17 4:43 ` Uwe Kleine-König
2022-08-01 21:44 broonie
2022-08-04 12:33 ` Mark Brown
2022-08-04 23:36 ` Jiri Kosina
2022-04-27 0:48 Stephen Rothwell
2022-04-27 6:53 ` Fabien Parent
2022-04-27 7:35 ` Lee Jones
2022-04-27 7:41 ` Fabien Parent
2022-05-02 2:17 ` Stephen Rothwell
2022-05-06 0:25 ` Dmitry Torokhov
2022-05-31 10:13 ` Fabien Parent
2020-03-25 7:16 Stephen Rothwell
2020-03-31 21:06 ` Stephen Rothwell
2015-10-16 2:19 Stephen Rothwell
2015-10-16 7:37 ` Hans de Goede
2015-10-17 16:39 ` Dmitry Torokhov
2015-07-24 1:49 Stephen Rothwell
2015-07-24 2:33 ` Dmitry Torokhov
2012-01-24 3:25 Stephen Rothwell
2012-01-24 6:59 ` Dmitry Torokhov
2012-01-24 23:16 ` John Stultz
2010-08-19 1:35 Stephen Rothwell
2010-08-19 5:19 ` Dmitry Torokhov
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=20121005061236.GA11112@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=killertofu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tianyu.lan@intel.com \
/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).