From: Borislav Petkov <bp@alien8.de>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Cc: tony.luck@intel.com, mchehab@osg.samsung.com,
arozansk@redhat.com, linux-edac@vger.kernel.org
Subject: [v1,1/4] EDAC, skx_edac: Fix function calling order in skx_exit()
Date: Fri, 16 Nov 2018 11:23:40 +0100 [thread overview]
Message-ID: <20181116102340.GB20313@zn.tnic> (raw)
On Fri, Nov 16, 2018 at 03:33:36PM +0800, Qiuxu Zhuo wrote:
> The order of function calling in skx_exit() is not the reversed
> order in skx_init(). Fix it by calling functions in skx_exit()
> in a proper order.
>
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> ---
> drivers/edac/skx_edac.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
All 4 applied, thanks.
Hint for the future: please teach your git to send the patches threaded,
i.e., the mail header should have:
In-Reply-To: <first mail's Message-ID>
References: <first mail's Message-ID>
Thx.
next reply other threads:[~2018-11-16 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:23 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-16 13:28 [v1,1/4] EDAC, skx_edac: Fix function calling order in skx_exit() Qiuxu Zhuo
2018-11-16 7:33 Qiuxu Zhuo
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=20181116102340.GB20313@zn.tnic \
--to=bp@alien8.de \
--cc=arozansk@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=qiuxu.zhuo@intel.com \
--cc=tony.luck@intel.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