From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
linux-stable@vger.kernel.org, Martin Svec <martin.svec@zoner.cz>,
Alex Gorbachev <ag@iss-integration.com>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 4.1] target-core: fix return without a value
Date: Tue, 10 Nov 2015 10:56:05 -0800 [thread overview]
Message-ID: <20151110185605.GA15668@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1511101329001.18857@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, Nov 10, 2015 at 01:32:10PM -0500, Mikulas Patocka wrote:
> Fix the warning drivers/target/target_core_pr.c:332:3: warning: 'return'
> with no value, in function returning non-void [-Wreturn-type]
>
> The patch 35afa65642a9a88c81913377b93a3a66220f8b9d committed to 4.1.11
> adds a check if device_list is NULL. The patch adds a return statement
> without a value to the function core_scsi3_pr_seq_non_holder that returns
> int.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> ---
> drivers/target/target_core_pr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2015-11-10 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 18:32 [PATCH 4.1] target-core: fix return without a value Mikulas Patocka
2015-11-10 18:56 ` Greg Kroah-Hartman [this message]
2015-11-10 23:31 ` Mikulas Patocka
2015-11-11 0:00 ` Greg Kroah-Hartman
2015-11-11 12:06 ` Mikulas Patocka
2015-11-11 12:15 ` [PATCH 4.1 v2] " Mikulas Patocka
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=20151110185605.GA15668@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ag@iss-integration.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=martin.svec@zoner.cz \
--cc=mpatocka@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.