From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Wentong Wu <wentong.wu@intel.com>,
gregkh@linuxfoundation.org, tomas.winkler@intel.com,
hdegoede@redhat.com, alexander.usyskin@intel.com,
zhifeng.wang@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device
Date: Wed, 29 Nov 2023 12:21:32 +0200 [thread overview]
Message-ID: <ZWcQrHs_fpqo80iX@smile.fi.intel.com> (raw)
In-Reply-To: <ZWcD18B916Xs1JiU@kekkonen.localdomain>
On Wed, Nov 29, 2023 at 09:26:47AM +0000, Sakari Ailus wrote:
> On Tue, Nov 28, 2023 at 08:34:06PM +0800, Wentong Wu wrote:
...
> I wouldn't mind having a single Kconfig option for the two drivers either.
> They're always used together, aren't they?
As far as I understand the topology, here we have one "core" driver and
one "leaf" driver. So, in my understanding they may not go together as
it will bring unneeded code in the future in some configurations.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-11-29 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:34 [PATCH 0/2] mei: Add support for IVSC device Wentong Wu
2023-11-28 12:34 ` [PATCH 1/2] mei: Add transport driver " Wentong Wu
2023-12-06 7:40 ` Winkler, Tomas
2023-11-28 12:34 ` [PATCH 2/2] mei: Add MEI hardware support " Wentong Wu
2023-11-28 22:50 ` kernel test robot
2023-11-29 9:26 ` Sakari Ailus
2023-11-29 10:21 ` Andy Shevchenko [this message]
2023-11-29 10:26 ` Sakari Ailus
2023-11-29 14:11 ` Wu, Wentong
2023-11-29 12:28 ` Krzysztof Kozlowski
2023-11-29 13:56 ` Wu, Wentong
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=ZWcQrHs_fpqo80iX@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@intel.com \
--cc=zhifeng.wang@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