From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
marex@denx.de, kernel@pengutronix.de
Subject: Re: [GIT PULL FOR v6.3] uvcgadget changes
Date: Tue, 24 Jan 2023 16:35:24 +0100 [thread overview]
Message-ID: <Y8/6vHUoB4WjbLk2@kroah.com> (raw)
In-Reply-To: <20230124144929.GB19219@pengutronix.de>
On Tue, Jan 24, 2023 at 03:49:29PM +0100, Michael Grzeschik wrote:
> The following changes since commit 82adfe34694c98f1115a7b75cff6af9c4a35dba9:
>
> Merge tag 'media-uvc-next-20230115' of git://git.kernel.org/pub/scm/linux/kernel/git/pinchartl/linux into media_stage (2023-01-22 08:43:14 +0100)
>
> are available in the Git repository at:
>
> git://git.pengutronix.de/mgr/linux tags/uvc-gadget-next-20230124
>
> for you to fetch changes up to e88f760d0f7054f49aa68b75bf0530840f031d34:
>
> usb: uvc: use v4l2_fill_fmtdesc instead of open coded format name (2023-01-24 15:26:07 +0100)
>
> ----------------------------------------------------------------
> Marek Vasut (1):
> media: uvcvideo: Add GUID for BGRA/X 8:8:8:8
>
> Michael Grzeschik (4):
> usb: uvc: move media/v4l2-uvc.h to usb/uvc.h
> usb: uvc: move uvc_fmts and uvc_format_by_guid to own compile unit
> usb: uvc: make uvc_format_desc table const
> usb: uvc: use v4l2_fill_fmtdesc instead of open coded format name
Sorry, but I can't take patches like this as a pull request. I want to
see the real patches and get people to review them properly that way.
thanks,
greg k-h
next prev parent reply other threads:[~2023-01-24 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 14:49 [GIT PULL FOR v6.3] uvcgadget changes Michael Grzeschik
2023-01-24 15:35 ` Greg KH [this message]
2023-01-24 16:17 ` Michael Grzeschik
2023-01-26 22:33 ` Michael Grzeschik
2023-01-26 22:48 ` Laurent Pinchart
2023-01-27 7:15 ` Greg KH
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=Y8/6vHUoB4WjbLk2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=marex@denx.de \
--cc=mgr@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