From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Rabin Vincent <rabin@rab.in>
Cc: Jesper Nilsson <jespern@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-cris-kernel <linux-cris-kernel@axis.com>
Subject: Re: [PATCH 1/2] CRISv32: add unreachable() to BUG()
Date: Sun, 17 May 2015 21:09:20 +0200 [thread overview]
Message-ID: <20150517190920.GP11161@axis.com> (raw)
In-Reply-To: <1431607016-6301-1-git-send-email-rabin@rab.in>
On Thu, May 14, 2015 at 02:36:55PM +0200, Rabin Vincent wrote:
> Add an unreachable() in the BUG() implementations, to get rid of
> several warnings similar to the one below:
>
> kernel/sched/core.c: In function 'pick_next_task':
> kernel/sched/core.c:2690:1: warning: control reaches end of non-void function [-Wreturn-type]
Thanks, applied!
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
prev parent reply other threads:[~2015-05-17 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 12:36 [PATCH 1/2] CRISv32: add unreachable() to BUG() Rabin Vincent
2015-05-14 12:36 ` [PATCH 2/2] CRISv32: allow CONFIG_DEBUG_BUGVERBOSE Rabin Vincent
2015-05-17 19:15 ` Jesper Nilsson
2015-05-17 19:09 ` Jesper Nilsson [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=20150517190920.GP11161@axis.com \
--to=jesper.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
/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;
as well as URLs for NNTP newsgroup(s).