From: Wolfram Sang <wsa@the-dreams.de>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: linux-kernel@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
kbuild-all@01.org, daniel.lezcano@linaro.org,
Haavard Skinnemoen <hskinnemoen@gmail.com>
Subject: Re: [PATCH] avr32: remove cpu_data macro to fix compiles
Date: Tue, 1 Apr 2014 11:55:22 +0200 [thread overview]
Message-ID: <20140401095521.GA3326@katana> (raw)
In-Reply-To: <20140224072820.GA9069@samfundet.no>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Mon, Feb 24, 2014 at 08:28:20AM +0100, Hans-Christian Egtvedt wrote:
> Around Sat 22 Feb 2014 09:28:27 +0100 or thereabout, Wolfram Sang wrote:
> > Having cpu_data as a parameterless macro can easily cause build failures
> > because it can be a variable name like in linux/pm_domain.h [1]. So,
> > remove the macro and convert its only user. Because this architecture
> > cannot do SMP, remove the whole SMP block, too. Only compile tested due
> > to no hardware.
>
> Looks sane, AVR32 doesn't support SMP, so this change should be fine.
>
> > Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> >
>
> Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>
>
> > [1] https://lists.01.org/pipermail/kbuild-all/2014-February/003252.html
> >
>
> clockevents/3.15 branch, mens what you have queued up for 3.15?
>
> I can queue this in my linux-next, and send Linus an early pull request the
> moment 3.14 is released.
Have you done this already? I can't find it, yet I see the pull request
for the clocks is already out.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-01 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53060d5d.XcmAdOiLt1MCo6Y5%fengguang.wu@intel.com>
2014-02-22 8:28 ` [PATCH] avr32: remove cpu_data macro to fix compiles Wolfram Sang
2014-02-24 7:28 ` Hans-Christian Egtvedt
2014-02-24 8:17 ` Wolfram Sang
2014-04-01 9:55 ` Wolfram Sang [this message]
2014-04-01 10:28 ` Hans-Christian Egtvedt
2014-04-01 10:39 ` Wolfram Sang
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=20140401095521.GA3326@katana \
--to=wsa@the-dreams.de \
--cc=daniel.lezcano@linaro.org \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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