From: Gregor Riepl <onitake@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Hans de Goede <hdegoede@redhat.com>
Cc: "Andy Shevchenko" <andy@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86: touchscreen_dmi: Add support for setting touchscreen properties from cmdline
Date: Sat, 25 May 2024 19:41:52 +0200 [thread overview]
Message-ID: <f6d5675c-7215-45a1-a99b-f811ca0c4e27@gmail.com> (raw)
In-Reply-To: <CAHp75VdTJbZru5M4d81dU2Wbu4=G26OAgVksFF8H8vRBWHeDfw@mail.gmail.com>
>> And the kind of refactoring of next_arg() you are asking for here
>> is way out of scope,
>
> Of course, of course, but why introduce Yet Another Parser to begin with?
>
>> so sorry but I don't plan to change this part
>> of the patch.
>
> This is not good.
> But I have no power to stop it, while being very sad about this attitude.
Andy, I do agree with you, but what would you suggest we can do about the situation?
Write a generic parser that everyone should use from now on, and then migrate all usage to this parser?
next prev parent reply other threads:[~2024-05-25 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 16:48 [PATCH] platform/x86: touchscreen_dmi: Add support for setting touchscreen properties from cmdline Hans de Goede
2024-05-22 17:19 ` Andy Shevchenko
2024-05-22 17:20 ` Andy Shevchenko
2024-05-22 18:40 ` Hans de Goede
2024-05-22 19:32 ` Andy Shevchenko
2024-05-22 19:34 ` Andy Shevchenko
2024-05-23 8:47 ` Hans de Goede
2024-05-25 14:07 ` Andy Shevchenko
2024-05-25 17:41 ` Gregor Riepl [this message]
2024-05-27 13:44 ` Andy Shevchenko
2024-05-22 19:01 ` Randy Dunlap
2024-05-23 9:48 ` Hans de Goede
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=f6d5675c-7215-45a1-a99b-f811ca0c4e27@gmail.com \
--to=onitake@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
/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.