All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 00:06:16 +0200	[thread overview]
Message-ID: <20140822220610.GB24037@mithrandir> (raw)
In-Reply-To: <20140823070737.371f09fb@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]

On Sat, Aug 23, 2014 at 07:07:37AM +1000, Stephen Rothwell wrote:
> Hi Thierry,
> 
> After merging the pwm tree, today's linux-next build (powerpc allyesconfig)
> failed like this:
> 
> drivers/pwm/pwm-lpss.c: In function 'pwm_lpss_config':
> drivers/pwm/pwm-lpss.c:81:2: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
>   ctrl = readl(lpwm->regs + PWM);
>   ^
> drivers/pwm/pwm-lpss.c:87:2: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
>   writel(ctrl, lpwm->regs + PWM);
>   ^
> 
> Caused by commit 28160b18787b ("pwm: lpss: Properly split driver to
> parts").
> 
> I have reverted that commit for today (and 06c7b5394e21 ("pwm: lpss:
> pci: Move to use pcim_enable_device()") which depends on it).

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?

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-08-22 22:06 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 [this message]
2014-08-22 22:15   ` Thierry Reding
2014-08-22 22:30     ` Stephen Rothwell
  -- 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=20140822220610.GB24037@mithrandir \
    --to=thierry.reding@gmail.com \
    --cc=andriy.shevchenko@linux.intel.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.