Linux backports project
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH] header: fix compile error on PowerPC (PPC_85xx)
Date: Thu, 05 Oct 2017 08:49:39 +0200	[thread overview]
Message-ID: <1507186179.2387.12.camel@sipsolutions.net> (raw)
In-Reply-To: <a47cbe26-26fb-cfb6-f7cd-17d77153ea66@hauke-m.de>

On Mon, 2017-10-02 at 20:31 +0200, Hauke Mehrtens wrote:
> On 10/02/2017 02:39 PM, Johannes Berg wrote:
> > On Sun, 2017-10-01 at 21:38 +0200, Hauke Mehrtens wrote:
> > > Including linux/interrupt.h in linux/hrtimer.h causes this error
> > > message
> > > on PowerPC builds on x86, ARM and MIPS it works:
> > 
> > I think I also saw this on x86 on older kernel versions, and
> > couldn't
> > really figure out what was causing it...
> 
> I haven't fully understood this issue, but the LEDE build bot found
> it
> on multiple PowerPC based systems. With this patch applied it is
> compiling on all targets.
> 
> I ran the build test script on the compat server and it was fine with
> this patch applied for all kernel versions that worked before.

Ok.

> > > The backport of the hrtimer_start() functions needs the
> > > linux/interrupt.h because some parts are defined there. Fix this
> > > by
> > > moving the hrtimer_start() backport to the linux/interrupt.h
> > > backport
> > > header file.
> > 
> > Does hrtimre.h always include interrupt.h, so that we get it in
> > when
> > somebody includes just hrtimer.h?
> 
> I do not know, it is not included directly.

I guess we'll find out :-)

I'll apply this.

thanks,
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

      reply	other threads:[~2017-10-05  6:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 19:38 [PATCH] header: fix compile error on PowerPC (PPC_85xx) Hauke Mehrtens
2017-10-02 12:39 ` Johannes Berg
2017-10-02 18:31   ` Hauke Mehrtens
2017-10-05  6:49     ` Johannes Berg [this message]

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=1507186179.2387.12.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.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