From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thierry Reding <thierry.reding@gmail•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Andy Shevchenko <andriy.shevchenko@linux•intel.com>
Subject: Re: linux-next: build failure after merge of the pwm tree
Date: Sat, 23 Aug 2014 08:30:09 +1000 [thread overview]
Message-ID: <20140823083009.395b76ba@canb.auug.org.au> (raw)
In-Reply-To: <20140822221540.GC24037@mithrandir>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
Hi Thierry,
On Sat, 23 Aug 2014 00:15:54 +0200 Thierry Reding <thierry.reding@gmail•com> wrote:
>
> On Sat, Aug 23, 2014 at 12:06:16AM +0200, Thierry Reding wrote:
> >
> > Ugh, that's unfortunate. I have a set of scripts I use to build-test
> > before pushing, but I don't usually do full allyesconfig builds. It
> > seems like pwm-lpss.c might only be missing a linux/io.h include. It
> > will likely be Monday before I find the time to properly test and fix
> > this, do you want me to remove the commits from the pwm/for-next branch
> > so you don't have to revert it again?
>
> Just confirmed that adding a linux/io.h include fixes the build. Will
> push a fix in a minute.
The revert would have happened automatically, but if it is fixed I will
remove it, thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-22 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 21:07 linux-next: build failure after merge of the pwm tree Stephen Rothwell
2014-08-22 22:06 ` Thierry Reding
2014-08-22 22:15 ` Thierry Reding
2014-08-22 22:30 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-12 6:01 Stephen Rothwell
2019-01-12 6:08 ` Stephen Rothwell
2019-01-12 15:27 ` Uwe Kleine-König
2023-12-21 5:58 Stephen Rothwell
2023-12-21 9:25 ` Thierry Reding
2023-12-21 10:09 ` Lee Jones
2023-12-21 12:13 ` Sean Young
2023-12-21 12:51 ` Lee Jones
[not found] <CGME20251027015241eucas1p1784b974d0c150e8c3513f32401205669@eucas1p1.samsung.com>
2025-10-27 1:51 ` Stephen Rothwell
2025-10-27 8:11 ` Uwe Kleine-König
2025-10-27 9:38 ` Danilo Krummrich
2025-10-28 1:51 ` Stephen Rothwell
2025-12-05 3:33 ` Stephen Rothwell
2025-10-27 13:40 ` Uwe Kleine-König
2025-10-27 13:49 ` Danilo Krummrich
2025-10-27 8:36 ` Michal Wilczynski
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=20140823083009.395b76ba@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=thierry.reding@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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