linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Sweet <msweet@msweet.org>
To: Paul Wise <pabs3@bonedaddy.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Matt Porter <mporter@kernel.crashing.org>,
	Krzysztof Opasiak <k.opasiak@samsung.com>,
	Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
	Karol Lewandowski <k.lewandowsk@samsung.com>,
	linux-usb@vger.kernel.org
Subject: Re: proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation?
Date: Fri, 26 Feb 2021 20:54:45 -0500	[thread overview]
Message-ID: <07846969-5243-4272-B27A-F821E8810856@msweet.org> (raw)
In-Reply-To: <f89e3e5b5e25b89a603e2d97542d60461b429910.camel@bonedaddy.net>

Paul,

> On Feb 26, 2021, at 8:08 PM, Paul Wise <pabs3@bonedaddy.net> wrote:
> 
> On Fri, 2021-02-26 at 14:24 -0500, Mike Sweet wrote:
> 
>> Paul, please add me (GitHub user michaelrsweet)
> 
> Invited, you should get an email about it.

Yes, thank you!

>> I’m gearing up to work on the USB gadget documentation
> 
> I guess you mean the documentation in the Linux kernel repository,
> I assume that the libusbgx/gt/gadgetd docs could use some work too.

Primarily the first, but I’ll likely create libusbgx examples.

>> Implementing IPP-USB has been an interesting challenge
> 
> Are talking about a IPP-USB device implementation?
> I can't find your implementation on your GitHub account,
> could you provide a link, or is the code proprietary?

It will soon show up in the PAPPL project alongside the other USB gadget bits. I’ve been prototyping in a private repo in preparation for adding it to PAPPL...

____________________
Michael Sweet

  reply	other threads:[~2021-02-27  1:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210119200737eucas1p12bfb53d11543ee2ccb1a4bc2138f6535@eucas1p1.samsung.com>
2021-01-19 20:06 ` proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation? Paul Wise
2021-01-19 20:15   ` Krzysztof Opasiak
2021-01-20 11:58     ` Andrzej Pietrasiewicz
2021-01-20 15:19   ` Greg Kroah-Hartman
2021-01-20 15:34     ` Michael Sweet
2021-01-20 15:39     ` Paul Wise
2021-01-25 15:02       ` Michael Grzeschik
2021-02-05 23:35     ` Paul Wise
2021-02-06 13:14       ` Greg Kroah-Hartman
2021-02-06 23:28         ` Paul Wise
2021-02-14  2:17           ` Paul Wise
2021-02-15  9:53             ` Andrzej Pietrasiewicz
2021-02-15 10:07               ` Greg Kroah-Hartman
2021-02-15 10:31                 ` Krzysztof Opasiak
2021-02-25 13:24             ` Paul Wise
2021-02-26 19:24               ` Mike Sweet
2021-02-27  1:08                 ` Paul Wise
2021-02-27  1:54                   ` Michael Sweet [this message]
2021-07-13  3:43   ` Paul Wise
2021-07-13  4:53     ` Greg KH
2021-07-13  5:40       ` Paul Wise
2021-07-13  6:37         ` Greg KH
2021-07-14  2:11           ` Paul Wise

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=07846969-5243-4272-B27A-F821E8810856@msweet.org \
    --to=msweet@msweet.org \
    --cc=andrzej.p@collabora.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=k.lewandowsk@samsung.com \
    --cc=k.opasiak@samsung.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mporter@kernel.crashing.org \
    --cc=pabs3@bonedaddy.net \
    /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).