From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sui Jingfeng <sui.jingfeng@linux.dev>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-acpi@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH] software node: Implement device_get_match_data fwnode callback
Date: Fri, 22 Mar 2024 20:16:38 +0200 [thread overview]
Message-ID: <Zf3LBvJEJF9xr2fv@smile.fi.intel.com> (raw)
In-Reply-To: <8afe3f27-fc8e-4c20-ba28-74a0a2937e55@linux.dev>
On Sat, Mar 23, 2024 at 02:12:14AM +0800, Sui Jingfeng wrote:
> On 2024/3/23 02:05, Andy Shevchenko wrote:
> > Besides that, the kernel project rule is "we do not add
> > the dead (unused) code".
>
> This rule is good an correct and I admit.
>
> But the problem is that it is chicken-and-egg problem,
> it probably have at least two user now.
Then show them! Convert in the same series and show that.
> it's possible that it will gain more users in the future.
>
> But if you reject everybody from now, then it is zero.
As a no-user patch, yes, I reject this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-03-22 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 23:42 [PATCH] software node: Implement device_get_match_data fwnode callback Sui Jingfeng
2024-03-20 10:39 ` Andy Shevchenko
2024-03-20 19:22 ` Sui Jingfeng
2024-03-20 20:28 ` Andy Shevchenko
2024-03-22 9:00 ` Sui Jingfeng
2024-03-22 16:14 ` Andy Shevchenko
2024-03-22 17:43 ` Sui Jingfeng
2024-03-22 18:05 ` Andy Shevchenko
2024-03-22 18:12 ` Sui Jingfeng
2024-03-22 18:16 ` Andy Shevchenko [this message]
2024-03-22 18:30 ` Sui Jingfeng
2024-03-25 13:41 ` 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=Zf3LBvJEJF9xr2fv@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sui.jingfeng@linux.dev \
--cc=vladimir.oltean@nxp.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