From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-c6x-dev@linux-c6x.org,
Aurelien Jacquiot <a-jacquiot@ti.com>,
Mark Salter <msalter@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 3/4] C6X/megamode-pic: Delete an unnecessary return statement in megamod_pic_init()
Date: Thu, 11 May 2017 15:48:36 +0200 [thread overview]
Message-ID: <7f92b7a6-1814-02f5-4026-8cfcdc1dfc6a@users.sourceforge.net> (raw)
In-Reply-To: <1b8c2efb-1096-3b78-9100-e20c55b6ecf1@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 11 May 2017 15:05:41 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected function.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
arch/c6x/platforms/megamod-pic.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/c6x/platforms/megamod-pic.c b/arch/c6x/platforms/megamod-pic.c
index cf0ebf25e42f..c49aa63289fa 100644
--- a/arch/c6x/platforms/megamod-pic.c
+++ b/arch/c6x/platforms/megamod-pic.c
@@ -339,6 +339,4 @@ void __init megamod_pic_init(void)
soc_ops.get_exception = get_exception;
soc_ops.assert_event = assert_event;
-
- return;
}
--
2.12.3
next prev parent reply other threads:[~2017-05-11 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 13:45 [PATCH 0/4] C64x+ Megamodule PIC: Adjustments for three functions SF Markus Elfring
2017-05-11 13:46 ` [PATCH 1/4] C6X/megamode-pic: Improve a size determination in init_megamod_pic() SF Markus Elfring
2017-05-11 13:47 ` [PATCH 2/4] C6X/megamode-pic: Delete an error message for a failed memory allocation " SF Markus Elfring
2017-05-11 13:48 ` SF Markus Elfring [this message]
2017-05-11 13:49 ` [PATCH 4/4] C6X/megamode-pic: Fix a typo in a comment line SF Markus Elfring
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=7f92b7a6-1814-02f5-4026-8cfcdc1dfc6a@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=a-jacquiot@ti.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.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
all inboxes | Powered by JetHome®