mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] usbip: Update to accomodate for hwdata package.
Date: Fri, 21 Jan 2022 08:19:38 +0100	[thread overview]
Message-ID: <20220121071938.1968729-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220108184518.3774572-5-christian.melki@t2data.com>

Thanks, applied as 301ccffc9ead2f4b598de4db9ff872818bdb5f4a.

Michael

[sent from post-receive hook]

On Fri, 21 Jan 2022 08:19:38 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Make usbip depend on hwdata-usb files.
> 
> Change directory here to /usr/share instead of changing
> all the other locations to /usr/share/hwdata.
> This is simpler, for now.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220108184518.3774572-5-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/usbip.in b/rules/usbip.in
> index 4455ce484cf0..3b6fb77a7520 100644
> --- a/rules/usbip.in
> +++ b/rules/usbip.in
> @@ -4,6 +4,8 @@ config USBIP
>  	tristate
>  	select UDEV
>  	select UDEV_LIBUDEV
> +	select HWDATA		if !SYSTEMD_HWDB
> +	select HWDATA_USB	if !SYSTEMD_HWDB
>  	prompt "usbip"
>  	help
>  	  USB/IP system for sharing USB devices over the network.
> diff --git a/rules/usbip.make b/rules/usbip.make
> index a85512147183..9d76ec5788be 100644
> --- a/rules/usbip.make
> +++ b/rules/usbip.make
> @@ -32,7 +32,7 @@ USBIP_CONF_TOOL	:= autoconf
>  USBIP_CONF_OPT	:= \
>  	$(CROSS_AUTOCONF_USR) \
>  	--without-tcp-wrappers \
> -	--with-usbids-dir=/usr/share/hwdata/ \
> +	--with-usbids-dir=/usr/share/ \
>  	--with-fortify
>  
>  # ----------------------------------------------------------------------------

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


  reply	other threads:[~2022-01-21  7:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 18:45 [ptxdist] [PATCH 0/7] Hwdata introduction Christian Melki
2022-01-08 18:45 ` [ptxdist] [PATCH 1/7] hwdata: New package Christian Melki
2022-01-21  7:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-08 18:45 ` [ptxdist] [PATCH 2/7] usbutils: Version bump 007 -> 014 Christian Melki
2022-01-21  7:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-08 18:45 ` [ptxdist] [PATCH 3/7] pciutils: Update to accomodate for hwdata package Christian Melki
2022-01-21  7:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-08 18:45 ` [ptxdist] [PATCH 4/7] usbip: " Christian Melki
2022-01-21  7:19   ` Michael Olbrich [this message]
2022-01-08 18:45 ` [ptxdist] [PATCH 5/7] libpciaccess: " Christian Melki
2022-01-21  7:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-08 18:45 ` [ptxdist] [PATCH 6/7] lshw: Version bump. B.02.14 -> B.02.19.2 + accomodation " Christian Melki
2022-01-21  7:19   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-08 18:45 ` [ptxdist] [PATCH 7/7] udev: Update to accomodate " Christian Melki
2022-01-21  7:19   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20220121071938.1968729-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --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