From: Michael Olbrich <mol@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] systemd: fix installation of 60-input-id.rules
Date: Sun, 14 Mar 2021 14:35:34 +0100 [thread overview]
Message-ID: <E1lLQu6-007JLk-Ve@dude03.red.stw.pengutronix.de> (raw)
In-Reply-To: <20210305092941.25892-1-m.felsch@pengutronix.de>
Thanks, applied as aed8313a34ad6b207fc396227de3d1fddfb16f87.
Michael
[sent from post-receive hook]
On Sun, 14 Mar 2021 14:35:34 +0100, Marco Felsch <m.felsch@pengutronix.de> wrote:
> This rule has a two lines:
> - one for the builtin "input_id" command and
> - one for the hwdb command.
>
> Only the second requires the hwdb. The first command can run without the
> hwdb and is necessary to tag the event devices correctly for the usage
> with libinput.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> Message-Id: <20210305092941.25892-1-m.felsch@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/systemd.make b/rules/systemd.make
> index d2393f8a639c..e9313cc24181 100644
> --- a/rules/systemd.make
> +++ b/rules/systemd.make
> @@ -288,6 +288,7 @@ SYSTEMD_UDEV_RULES-y := \
> 60-persistent-storage.rules \
> 60-block.rules \
> 60-drm.rules \
> + 60-input-id.rules \
> 60-serial.rules \
> 64-btrfs.rules \
> 75-net-description.rules \
> @@ -298,7 +299,6 @@ SYSTEMD_UDEV_RULES-y := \
> SYSTEMD_UDEV_RULES-$(PTXCONF_SYSTEMD_UDEV_HWDB) += \
> 60-autosuspend.rules \
> 60-evdev.rules \
> - 60-input-id.rules \
> 60-sensor.rules \
> 70-joystick.rules \
> 70-mouse.rules \
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-03-14 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 9:29 [ptxdist] [PATCH] " Marco Felsch
2021-03-14 13:35 ` Michael Olbrich [this message]
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=E1lLQu6-007JLk-Ve@dude03.red.stw.pengutronix.de \
--to=mol@pengutronix.de \
--cc=m.felsch@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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