From: "Chanwoo Choi" <cw00.choi@samsung.com>
To: "'Andy Shevchenko'" <andriy.shevchenko@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Cc: "'MyungJoo Ham'" <myungjoo.ham@samsung.com>
Subject: RE: [PATCH v1 1/1] extcon: intel-mrfld: Switch to use dev_err_probe()
Date: Thu, 22 Feb 2024 14:45:51 +0900 [thread overview]
Message-ID: <001001da6552$64c02a90$2e407fb0$@samsung.com> (raw)
In-Reply-To: <ZdYOPISUzbjid9l8@smile.fi.intel.com>
> -----Original Message-----
> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Sent: Wednesday, February 21, 2024 11:53 PM
> To: linux-kernel@vger.kernel.org
> Cc: MyungJoo Ham <myungjoo.ham@samsung.com>; Chanwoo Choi
> <cw00.choi@samsung.com>
> Subject: 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@linux.intel.com) be applied?
>
> Ping?
>
> It's more than two months passed...
>
I'm sorry for late reply. I applied it. Thanks.
Best Regards,
Chanwoo Choi
next prev parent reply other threads:[~2024-02-22 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 16:19 [PATCH v1 1/1] extcon: intel-mrfld: Switch to use dev_err_probe() Andy Shevchenko
2024-02-01 12:09 ` Andy Shevchenko
2024-02-21 14:52 ` Andy Shevchenko
2024-02-22 1:53 ` MyungJoo Ham
2024-02-22 5:45 ` Chanwoo Choi [this message]
2024-02-22 13:18 ` 'Andy Shevchenko'
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='001001da6552$64c02a90$2e407fb0$@samsung.com' \
--to=cw00.choi@samsung.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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 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.