From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "Markus Elfring" <Markus.Elfring@web.de>,
linux-usb@vger.kernel.org, "Ajay Gupta" <ajayg@nvidia.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Haotien Hsu" <haotienh@nvidia.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Utkarsh Patel" <utkarsh.h.patel@intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Wolfram Sang" <wsa@the-dreams.de>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/2] usb: typec: ucsi: ccg: Adjustments for common code in two functions
Date: Thu, 26 Sep 2024 15:27:31 +0300 [thread overview]
Message-ID: <ZvVTMyn9VtuT-tIr@smile.fi.intel.com> (raw)
In-Reply-To: <CAA8EJpo0Q0Wn-GzqmPeNFfG_Hr-o8E7F_VuO47EbxKx=0OQhyQ@mail.gmail.com>
On Thu, Sep 26, 2024 at 02:20:19PM +0200, Dmitry Baryshkov wrote:
> On Thu, 26 Sept 2024 at 14:12, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Sep 26, 2024 at 12:26:24AM +0300, Dmitry Baryshkov wrote:
...
> > but in any case the thing is that kfree()
> > probably can be done using __free(). Then PM runtime handled differently.
>
> That's a separate cleanup in my opinion.
Yes and for that we do not need an intermediate change, right?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-26 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 17:31 [PATCH 0/2] usb: typec: ucsi: ccg: Adjustments for common code in two functions Markus Elfring
2024-09-25 17:32 ` [PATCH 1/2] usb: typec: ucsi: ccg: Use common code in ccg_write() Markus Elfring
2024-09-26 14:53 ` Heikki Krogerus
2024-09-25 17:33 ` [PATCH 2/2] usb: typec: ucsi: ccg: Use common code in ccg_read() Markus Elfring
2024-09-26 14:54 ` Heikki Krogerus
2024-09-25 21:26 ` [PATCH 0/2] usb: typec: ucsi: ccg: Adjustments for common code in two functions Dmitry Baryshkov
2024-09-26 12:12 ` Andy Shevchenko
2024-09-26 12:20 ` Dmitry Baryshkov
2024-09-26 12:27 ` Andy Shevchenko [this message]
2024-09-26 12:31 ` Dmitry Baryshkov
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=ZvVTMyn9VtuT-tIr@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Markus.Elfring@web.de \
--cc=ajayg@nvidia.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=haotienh@nvidia.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.com \
--cc=utkarsh.h.patel@intel.com \
--cc=wsa@the-dreams.de \
/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