mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Franck Jullien <franck.jullien@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: [PATCH] openrisc: fix call to restart_handler_register_fn
Date: Wed, 29 Mar 2017 15:45:04 +0200	[thread overview]
Message-ID: <CAJfOKBxJ0FwF0VBpeDTxe7cvgxmTW2xYHoCgXNAL+q+=9v=O6Q@mail.gmail.com> (raw)
In-Reply-To: <20170329064253.4rsnyzsfuaxzlm42@pengutronix.de>

2017-03-29 8:42 GMT+02:00 Sascha Hauer <s.hauer@pengutronix.de>:
> On Fri, Mar 24, 2017 at 08:35:22PM +0100, Franck Jullien wrote:
>> Signed-off-by: Franck Jullien <franck.jullien@gmail.com>
>> ---
>>  arch/openrisc/cpu/cpu.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/openrisc/cpu/cpu.c b/arch/openrisc/cpu/cpu.c
>> index d52b021..e7f9445 100644
>> --- a/arch/openrisc/cpu/cpu.c
>> +++ b/arch/openrisc/cpu/cpu.c
>> @@ -41,6 +41,6 @@ static void __noreturn openrisc_restart_cpu(struct restart_handler *rst)
>>
>>  static int restart_register_feature(void)
>>  {
>> -     restart_handler_register_fn(openrisc_restart_cpu, NULL, RESET_SCOPE_CPU);
>> +     return restart_handler_register_fn(openrisc_restart_cpu);
>>  }
>
> Applied, thanks. It seems I have disabled my openrisc autobuild at some
> point. Just re-enabled it. Normally such build failures shouldn't
> happen.
>

FYI, you can get the lastest toolchain here:

https://github.com/openrisc/or1k-gcc/releases/tag/or1k-5.4.0-20170218

Franck.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-03-29 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 19:35 Franck Jullien
2017-03-29  6:42 ` Sascha Hauer
2017-03-29 13:45   ` Franck Jullien [this message]
2017-04-04  6:46     ` Sascha Hauer

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='CAJfOKBxJ0FwF0VBpeDTxe7cvgxmTW2xYHoCgXNAL+q+=9v=O6Q@mail.gmail.com' \
    --to=franck.jullien@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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