[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240222015355epcms1p36eb91aa458c336900a52af653a5b7a44@epcms1p3>
Date: Thu, 22 Feb 2024 10:53:55 +0900
From: MyungJoo Ham <myungjoo.ham@...sung.com>
To: Chanwoo Choi <cw00.choi@...sung.com>
CC: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Re: [PATCH v1 1/1] extcon: intel-mrfld: Switch to use
dev_err_probe()
>
>---------Original Message---------
>Sender: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>Date: 2024-02-21 23:52 (GMT+9)
>Title: Re: [PATCH v1 1/1] extcon: intel-mrfld: Switch to use dev_err_probe()
>
>On Thu, Feb 01, 2024 at 02:09:23PM +0200, Andy Shevchenko wrote:
>> On Fri, Dec 22, 2023 at 06:19:54PM +0200, Andy Shevchenko wrote:
>> > Switch to use dev_err_probe() to simplify the error path and
>> > unify a message template.
>>
>> Any comments? Can these two patches (with
>> 20231222161854.2955859-1-andriy.shevchenko@...ux.intel.com) be applied?
>
>Ping?
>
>It's more than two months passed...
The patch "extcon: intel-mrfld: Switch to use dev_err_probe()"
looked good to me.
Chanwoo, please take a look.
Acked-by: MyungJoo Ham <myungjoo.ham@...sung.com>
Powered by blists - more mailing lists