From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Scally <dan.scally@ideasonboard.com>
Cc: linux-usb@vger.kernel.org, laurent.pinchart@ideasonboard.com,
mgr@pengutronix.de, balbi@kernel.org,
kieran.bingham@ideasonboard.com, torleiv@huddly.com,
stern@rowland.harvard.edu
Subject: Re: [PATCH v4 00/11] Add XU support to UVC Gadget
Date: Mon, 6 Feb 2023 11:29:08 +0100 [thread overview]
Message-ID: <Y+DWdLJng2IW7vAe@kroah.com> (raw)
In-Reply-To: <18f2b583-b355-9f6a-fb0f-fcfb41c168d9@ideasonboard.com>
On Mon, Feb 06, 2023 at 10:24:03AM +0000, Dan Scally wrote:
> Hi Greg
>
> On 06/02/2023 10:02, Greg KH wrote:
> > On Thu, Feb 02, 2023 at 01:54:57PM +0000, Daniel Scally wrote:
> > > Hello all
> > >
> > > This series adds support for the definition of extension units in configfs for
> > > the UVC Gadget. The XUs are modelled as config_items within a new "extensions"
> > > group under control, which seemed like an appropriate place to put them.
> > >
> > > To allow the XU's to be inserted in the function graph, the bSourceID attribute
> > > for the default output terminal is made writeable - users will need to configure
> > > it with the bUnitID of the XU that they want to use as the OT's source. This does
> > > mean that the XUs can _only_ be placed immediately preceding the OT, but I think
> > > that that's fine for now.
> > >
> > > The XUs configured through this series have been tested via uvc-gadget, uvcvideo
> > > and uvcdynctrl.
> > >
> > > This version is almost identical to v3 but rebased onto usb-testing, with minor
> > > changes to 6/11 and 7/11.
> > >
> > > v2 of the series here: https://lore.kernel.org/linux-usb/0ae65812-c937-d071-455b-7c1d6418b080@ideasonboard.com/
> > This series conflicts with the previous patch series you sent, how did
> > you create this?
>
>
> Do you mean conflicts with the previous version of this series, or with the
> "UVC Gadget: Extend color matching support" series? If the latter I rebased
> them separately onto usb-testing, so neither series knew about the other.
The latter. And if they know nothing about each other, how is anyone
supposed to be able to apply both of them?
Please please please make my life easy to take your changes, not
difficult, as this just makes me want to ignore your patches as I will
inherently assume they are going to cause me problems...
What would you do if you were in my place here?
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-06 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 13:54 [PATCH v4 00/11] Add XU support to UVC Gadget Daniel Scally
2023-02-02 13:54 ` [PATCH v4 01/11] usb: gadget: uvc: Make bSourceID read/write Daniel Scally
2023-02-02 13:54 ` [PATCH v4 02/11] usb: gadget: uvc: Generalise helper functions for reuse Daniel Scally
2023-02-02 13:55 ` [PATCH v4 03/11] usb: gadget: uvc: Allow definition of XUs in configfs Daniel Scally
2023-02-02 13:55 ` [PATCH v4 04/11] usb: gadget: uvc: Copy XU descriptors during .bind() Daniel Scally
2023-02-02 13:55 ` [PATCH v4 05/11] usb: gadget: configfs: Rename struct gadget_strings Daniel Scally
2023-02-02 13:55 ` [PATCH v4 06/11] usb: gadget: configfs: Support arbitrary string descriptors Daniel Scally
2023-02-02 13:55 ` [PATCH v4 07/11] usb: gadget: configfs: Attach arbitrary strings to cdev Daniel Scally
2023-02-02 13:55 ` [PATCH v4 08/11] usb: gadget: uvc: Allow linking XUs to string descriptors Daniel Scally
2023-02-02 13:55 ` [PATCH v4 09/11] usb: gadget: uvc: Pick up custom string descriptor IDs Daniel Scally
2023-02-02 13:55 ` [PATCH v4 10/11] usb: gadget: uvc: Allow linking function to string descs Daniel Scally
2023-02-02 13:55 ` [PATCH v4 11/11] usb: gadget: uvc: Use custom strings if available Daniel Scally
2023-02-06 10:02 ` [PATCH v4 00/11] Add XU support to UVC Gadget Greg KH
2023-02-06 10:24 ` Dan Scally
2023-02-06 10:29 ` Greg KH [this message]
2023-02-06 10:54 ` Dan Scally
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=Y+DWdLJng2IW7vAe@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-usb@vger.kernel.org \
--cc=mgr@pengutronix.de \
--cc=stern@rowland.harvard.edu \
--cc=torleiv@huddly.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 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.