From: Jiri Kosina <jikos@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"João Paulo Rechi Vita" <jprvita@gmail.com>,
"David Arcari" <darcari@redhat.com>
Subject: Re: linux-next: build failure after merge of the hid tree
Date: Mon, 12 Dec 2016 09:50:40 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1612120950140.16984@cbobk.fhfr.pm> (raw)
In-Reply-To: <20161212105903.418e913f@canb.auug.org.au>
On Mon, 12 Dec 2016, Stephen Rothwell wrote:
> Hi Jiri,
>
> After merging the hid tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/hid/i2c-hid/i2c-hid.c: In function 'i2c_hid_start':
> drivers/hid/i2c-hid/i2c-hid.c:773:19: error: 'struct i2c_hid' has no member named 'irq'
> disable_irq(ihid->irq);
> ^
> drivers/hid/i2c-hid/i2c-hid.c:777:18: error: 'struct i2c_hid' has no member named 'irq'
> enable_irq(ihid->irq);
> ^
>
> Caused by commit
>
> de3c99488609 ("HID: i2c-hid: Disable IRQ before freeing buffers")
>
> interacting with commit
>
> ba18a9314a94 ("Revert "HID: i2c-hid: Add support for ACPI GPIO interrupts"")
>
> from earlier in the same tree!
>
> I have used the hid tree from next-20161209 for today.
I've now pushed out fixed for-next branch. Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2016-12-12 8:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 23:59 linux-next: build failure after merge of the hid tree Stephen Rothwell
2016-12-12 8:50 ` Jiri Kosina [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-07 1:06 Stephen Rothwell
2024-05-07 7:22 ` Kenny Levinsen
2024-04-11 0:51 Stephen Rothwell
2024-04-11 7:17 ` Benjamin Tissoires
2024-02-28 3:56 Stephen Rothwell
2022-07-25 0:40 Stephen Rothwell
2022-07-25 9:42 ` Jiri Kosina
2022-07-27 1:11 ` Stephen Rothwell
2021-12-03 7:01 Stephen Rothwell
2021-12-03 8:09 ` Greg Kroah-Hartman
2021-05-27 5:26 Stephen Rothwell
2021-05-27 8:14 ` Jiri Kosina
2021-05-27 8:25 ` Hans de Goede
2021-05-27 13:22 ` Naresh Kamboju
2021-05-27 13:42 ` Jiri Kosina
2019-10-04 0:28 Stephen Rothwell
2019-10-04 6:55 ` Hans de Goede
2012-06-29 2:47 Stephen Rothwell
2012-06-29 13:03 ` Jiri Kosina
2011-12-19 1:34 Stephen Rothwell
2011-12-19 8:21 ` Jiri Kosina
2011-11-29 1:00 Stephen Rothwell
2011-11-29 1:30 ` Jeremy Fitzhardinge
2011-06-08 3:03 Stephen Rothwell
2011-06-08 7:26 ` Stefan Kriwanek
2011-06-08 7:50 ` Jiri Kosina
2011-04-07 1:06 Stephen Rothwell
2011-04-07 13:00 ` Alan Ott
2011-04-08 23:54 ` Jiri Kosina
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=alpine.LNX.2.00.1612120950140.16984@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=darcari@redhat.com \
--cc=jprvita@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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.