public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Avichal Rakesh <arakesh@google.com>,
	dan.scally@ideasonboard.com, thinh.nguyen@synopsys.com,
	etalvala@google.com, jchowdhary@google.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3] usb: gadget: uvc: clean up comments and styling in video_pump
Date: Sun, 4 Jun 2023 10:55:04 +0300	[thread overview]
Message-ID: <20230604075504.GQ26944@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2023060434-reveler-twice-d92e@gregkh>

Hi Greg,

On Sun, Jun 04, 2023 at 09:43:40AM +0200, Greg KH wrote:
> On Fri, Jun 02, 2023 at 03:04:55PM -0700, Avichal Rakesh wrote:
> > This patch elaborates on some of the edge cases handled by
> > video_pump around setting no_interrupt flag, and brings the
> > code style in line with rest of the file.
> 
> When you say "and" that usually means it should be a separate patch.
> 
> But I really don't see what coding style changes you made here, what was
> it?
> 
> I can't see any logical changes made here, am I missing them?  Or is
> this all just a style-cleanup patch?

It's all style cleanup (variable declaration ordering), typo fixes, and
naming and documentation improvement, yes. I reviewed Avichal's original
patch when coming back from holidays, neither of us realizing that you
had merged it already. He sent a v2 and got told to rebase it on top of
your tree.  That's what v3 is, just handling the review comments.

I generally ask for patches to be split with one change per patch, but
given the small changes bundled here, and the fact that all of this just
incorporates the review comments, I think it would be a bit overkill.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-06-04  7:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 23:11 [PATCH] usb: gadget: uvc: queue empty isoc requests if no video buffer is available Avichal Rakesh
2023-06-02 15:19 ` Laurent Pinchart
2023-06-02 20:37   ` [PATCH v2] " Avichal Rakesh
2023-06-02 21:16     ` Thinh Nguyen
2023-06-02 22:00       ` Avichal Rakesh
2023-06-02 22:04       ` [PATCH v3] usb: gadget: uvc: clean up comments and styling in video_pump Avichal Rakesh
2023-06-04  7:43         ` Greg KH
2023-06-04  7:55           ` Laurent Pinchart [this message]
2023-06-07 20:28             ` Avichal Rakesh
2023-06-04  7:54         ` Laurent Pinchart
2023-06-02 20:39   ` [PATCH] usb: gadget: uvc: queue empty isoc requests if no video buffer is available Avichal Rakesh

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=20230604075504.GQ26944@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=arakesh@google.com \
    --cc=dan.scally@ideasonboard.com \
    --cc=etalvala@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jchowdhary@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=thinh.nguyen@synopsys.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