[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tencent_47C96C376F2E810C2237848B@qq.com>
Date: Mon, 16 Jul 2018 17:46:12 +0800
From: "陈华才" <chenhc@...ote.com>
To: "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
Cc: "linux-kernel" <linux-kernel@...r.kernel.org>,
"stable" <stable@...r.kernel.org>,
"Paul Burton" <paul.burton@...s.com>,
"James Hogan" <jhogan@...nel.org>
Subject: Re: [PATCH 4.9 03/32] MIPS: Use async IPIs forarch_trigger_cpumask_backtrace()
Just change "call_single_data_t" to "struct call_single_data" and everything is OK.
Huacai
------------------ Original ------------------
From: "Greg Kroah-Hartman"<gregkh@...uxfoundation.org>;
Date: Mon, Jul 16, 2018 05:40 PM
To: "陈华才"<chenhc@...ote.com>;
Cc: "linux-kernel"<linux-kernel@...r.kernel.org>; "stable"<stable@...r.kernel.org>; "Paul Burton"<paul.burton@...s.com>; "James Hogan"<jhogan@...nel.org>; "Ralf Baechle"<ralf@...ux-mips.org>; "linux-mips"<linux-mips@...ux-mips.org>;
Subject: Re: [PATCH 4.9 03/32] MIPS: Use async IPIs forarch_trigger_cpumask_backtrace()
On Mon, Jul 16, 2018 at 05:29:05PM +0800, 陈华才 wrote:
> Hi, Greg,
>
> kernel-4.9 doesn't have call_single_data_t, we should use struct call_single_data instead.
Can you send me a patch to merge with this one with that change so that
I know I get it right?
thanks,
greg k-h
Powered by blists - more mailing lists