From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/2] Input: silead - Always support 10 fingers
Date: Thu, 30 May 2024 16:54:53 -0700 [thread overview]
Message-ID: <ZlkRzbF_T8vgzxcr@google.com> (raw)
In-Reply-To: <9103e7ae-70f4-4ca0-a18d-322bdedbbdba@redhat.com>
On Mon, May 27, 2024 at 09:46:54AM +0200, Hans de Goede wrote:
> Hi,
>
> On 5/26/24 6:19 AM, Dmitry Torokhov wrote:
> > On Sat, May 25, 2024 at 09:38:52PM +0200, Hans de Goede wrote:
> >> Hi all,
> >>
> >> The first patch in this series stops making the maximum number of supported
> >> fingers in silead_ts configurable, replacing this with simply hardcoding it
> >> to 10.
> >>
> >> The main reason for doing so is to avoid the need to have a boiler-plate
> >> "silead,max-fingers=10" property in each silead touchscreen config.
> >> The second patch removes this boilerplate from all silead touchscreen
> >> configs in touchscreen_dmi.c .
> >>
> >> Dmitry, since touchscreen_dmi.c sees regular updates I believe it is
> >> best to merge the 2 patches separately. As long as I know that patch 1/2
> >> is queued for merging for say 6.11 then I can merge patch 2/2 independently
> >> for the same cycle.
> >
> > Why don't you merge both of them with my ack for the silead.c?
>
> That works for me too, thanks.
>
> One challenge here is that I typically send out new touchscreen_dmi
> entries as fixes. Are you ok with merging the silead change as a fix
> too ?
Sorry, I am not sure what you mean here. Do you mean you do not want to
wait for the next merge window and send it earlier? If so I'm fine with
it.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-05-30 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 19:38 [PATCH 0/2] Input: silead - Always support 10 fingers Hans de Goede
2024-05-25 19:38 ` [PATCH 1/2] " Hans de Goede
2024-05-26 4:20 ` Dmitry Torokhov
2024-05-25 19:38 ` [PATCH 2/2] platform/x86: touchscreen_dmi: Drop "silead,max-fingers" property Hans de Goede
2024-05-26 4:19 ` [PATCH 0/2] Input: silead - Always support 10 fingers Dmitry Torokhov
2024-05-27 7:46 ` Hans de Goede
2024-05-30 23:54 ` Dmitry Torokhov [this message]
2024-05-31 6:25 ` Hans de Goede
2024-06-03 9:14 ` 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=ZlkRzbF_T8vgzxcr@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-input@vger.kernel.org \
--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.