From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Duncan <leeman.duncan@gmail.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>,
stable@vger.kernel.org, Lee Duncan <lduncan@suse.com>
Subject: Re: [PATCH] fnic: fixup patch to resolve stack frame issues
Date: Wed, 27 Jan 2021 08:46:08 +0100 [thread overview]
Message-ID: <YBEaQEs6gvrSm6dA@kroah.com> (raw)
In-Reply-To: <20210127012124.22241-1-leeman.duncan@gmail.com>
On Tue, Jan 26, 2021 at 05:21:24PM -0800, Lee Duncan wrote:
> From: Hannes Reinecke <hare@suse.de>
>
> Commit 42ec15ceaea7 fixed a gcc issue with unused variables, but
> introduced errors since it allocated an array of two u64-s but
> then used more than that. Set the arrays to the proper size.
>
> Fixes: 42ec15ceaea74b5f7a621fc6686cbf69ca66c4cf
Please use the documented way to show sha1 commit ids to make it easier
to understand:
42ec15ceaea7 ("scsi: fnic: fix invalid stack access")
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-27 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 1:21 [PATCH] fnic: fixup patch to resolve stack frame issues Lee Duncan
2021-01-27 3:17 ` Lee Duncan
2021-01-27 7:46 ` Greg KH [this message]
2021-01-27 14:53 ` Lee Duncan
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=YBEaQEs6gvrSm6dA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=lduncan@suse.com \
--cc=leeman.duncan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox