From: David Miller <davem@davemloft.net>
To: osmith@sysmocom.de
Cc: netdev@vger.kernel.org, laforge@gnumonks.org
Subject: Re: Missing include include acpi.h causes build failures
Date: Mon, 06 Sep 2021 13:08:17 +0100 (BST) [thread overview]
Message-ID: <20210906.130817.2086973831700819915.davem@davemloft.net> (raw)
In-Reply-To: <aa6271d7-7574-041d-ab35-ea98a8a6df79@sysmocom.de>
From: Oliver Smith <osmith@sysmocom.de>
Date: Mon, 6 Sep 2021 11:04:40 +0200
> Hello linux-netdev ML,
>
> can somebody please cherry pick the following patch from
> torvalds/linux.git to net-next.git (or rebase on that patch? not sure
> about the usual workflow for net-next):
>
> ea7b4244 ("x86/setup: Explicitly include acpi.h")
>
> Since the 1st of September, this missing include causes the Osmocom CI
> job to fail, which runs osmo-ggsn against the GTP tunnel driver in
> net-next.git (to catch regressions in both kernel and Osmocom code).
I ff'd net-next ad this should be fixed now.
next prev parent reply other threads:[~2021-09-06 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 9:04 Missing include include acpi.h causes build failures Oliver Smith
2021-09-06 12:08 ` David Miller [this message]
2021-09-07 13:20 ` Harald Welte
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=20210906.130817.2086973831700819915.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=osmith@sysmocom.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