linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolai Kondrashov <spbnick@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: merge usbhid-dump into usbutils repo?
Date: Tue, 7 May 2019 16:29:02 +0200	[thread overview]
Message-ID: <20190507142902.GA29491@kroah.com> (raw)
In-Reply-To: <8f35c8e9-9ee0-a883-30e4-8b532316137d@gmail.com>

On Tue, May 07, 2019 at 05:23:05PM +0300, Nikolai Kondrashov wrote:
> Hi Greg,
> 
> On 5/7/19 5:00 PM, Greg KH wrote:
> > So, what do you think about the two options here?
> 
> I would absolutely be glad if you could take usbhid-dump under your wing!
> 
> I have little time for the DIGImend project these days, for which it was
> developed. I have a bit of financing from Patreon and occasional tablet
> manufacturer to work on the drivers, but that leaves very little time for the
> tools.
> 
> I wouldn't mind submitting any patches required to usbutils repo instead.
> And it's true the thing haven't needed much updates recently.
> Please also feel free to adjust it to your tastes too.
> 
> Thanks for looking after it!

Wonderful, so for now, I'll push what I have done with the merging of
the two repos together and make a public 012 release of usbutils, to fix
the issues the distros have already pointed out with usbhid-dump being
gone.

And then we can go from there forward, thanks for the quick response!

> P.S. It's awesome to see you receive Red Hat's Kernel CI effort so
> positively. Everyone's cheering for your feedback every time here :)

Hey, people testing my stable queue in a very-fast manner, why wouldn't
I like it?  :)

thanks,

greg k-h

      reply	other threads:[~2019-05-07 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 14:00 merge usbhid-dump into usbutils repo? Greg KH
2019-05-07 14:23 ` Nikolai Kondrashov
2019-05-07 14:29   ` Greg KH [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=20190507142902.GA29491@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=spbnick@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).