From: Jiri Kosina <jikos@kernel.org>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"Mario Limonciello" <superm1@gmail.com>,
"Filipe Laíns" <lains@archlinux.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Peter Hutterer" <peter.hutterer@redhat.com>,
"Richard Hughes" <hughsient@gmail.com>
Subject: Re: [PATCH] HID: logitech-dj: issue udev change event on device connection
Date: Sat, 21 Mar 2020 01:05:59 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2003210103540.19500@cbobk.fhfr.pm> (raw)
In-Reply-To: <20200319022331.GA2384843@jelly>
On Thu, 19 Mar 2020, Peter Hutterer wrote:
> > Then we would need to support that attribute forever. IMHO the best
> > option is to just make a uname call and check the kernel version, with
> > the code marked to be removed in the future when kernels older then
> > $version are no longer something we want to support.
Oh, this doesn't work *at all* with distro kernels backporting everything
that passess by to kernels with major versions looking years old.
I (as one of the "guilty ones" with my distro hat on) am not at all saying
it's perfect, but that's the way it is.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2020-03-21 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 16:19 [PATCH] HID: logitech-dj: issue udev change event on device connection Filipe Laíns
2020-03-18 17:15 ` Mario Limonciello
2020-03-18 17:20 ` Hans de Goede
2020-03-19 2:23 ` Peter Hutterer
2020-03-21 0:05 ` Jiri Kosina [this message]
[not found] ` <CA+EcB1P0qW4hdWG1YAYkD6X8jL1OaXZn4Lfu7aCmGBqwOPrJyA@mail.gmail.com>
2020-03-21 0:29 ` Peter Hutterer
2020-03-18 19:23 ` Filipe Laíns
2020-03-18 19:27 ` [PATCH v2] " Filipe Laíns
2020-03-24 10:20 ` Bastien Nocera
2020-03-24 13:46 ` Filipe Laíns
2020-03-24 14:03 ` Bastien Nocera
2020-03-24 14:10 ` Filipe Laíns
2020-03-24 14:24 ` Bastien Nocera
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=nycvar.YFH.7.76.2003210103540.19500@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hughsient@gmail.com \
--cc=lains@archlinux.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@redhat.com \
--cc=peter.hutterer@who-t.net \
--cc=superm1@gmail.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;
as well as URLs for NNTP newsgroup(s).