All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Dan Streetman <dan.streetman@canonical.com>
Cc: linux-bluetooth@vger.kernel.org,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Marcel Holtmann" <marcel@holtmann.org>,
	"Kay Sievers" <kay.sievers@vrfy.org>,
	systemd-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Subject: Re: Follow up on hid2hci: Fix udev rules for linux-4.14+
Date: Wed, 28 Aug 2019 20:50:51 +0300	[thread overview]
Message-ID: <20190828175051.GK7482@intel.com> (raw)
In-Reply-To: <CAOZ2QJOZStRYa=5fyod_AEJcJQw90_yX40dPYY3Dhvfso1e=RA@mail.gmail.com>

On Wed, Aug 28, 2019 at 01:34:07PM -0400, Dan Streetman wrote:
> It looks like this patch got lost at some point:
> https://lore.kernel.org/patchwork/patch/902126/#1138115
> 
> but it seems to still be a problem and I'd like to pull it into Ubuntu:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759836
> 
> Ville, did you ever follow up with a v2 for that patch and/or do you
> know if it will be accepted soon?

There's a more recent version of that somewhere on the mailing list.
The problem is getting someone to actually apply it. Seems much harder
than it should be...

And IIRC I also posted a few other fixes for hid2hci tool which didn't
get any response from the crowd.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2019-08-28 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 17:34 Follow up on hid2hci: Fix udev rules for linux-4.14+ Dan Streetman
2019-08-28 17:50 ` Ville Syrjälä [this message]
2019-08-28 17:59   ` Ville Syrjälä
2019-08-28 18:42     ` Dan Streetman

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=20190828175051.GK7482@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dan.streetman@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=zbyszek@in.waw.pl \
    /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.