From: Joe Perches <joe@perches.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/7] media: uvcvideo: Use pr_cont() macro
Date: Thu, 05 Nov 2020 10:58:45 -0800 [thread overview]
Message-ID: <92c85080ad6e1ded9c15479efe79a7eb7b0c7ee2.camel@perches.com> (raw)
In-Reply-To: <CANiDSCt8twP=JTkGjSVKdDwRhuHb7Jkv+=08U6oFdGtAjtrELw@mail.gmail.com>
On Thu, 2020-11-05 at 10:50 +0100, Ricardo Ribalda wrote:
> Hi Joe
Rehi Ricardo.
> On Thu, Nov 5, 2020 at 12:59 AM Joe Perches <joe@perches.com> wrote:
> > It looks as if all the pr_cont uses in the code are odd and repetitive.
> >
> > Perhaps it'd be sensible to add something like:
>
> Looks like a great idea. Queued for my v3
>
> https://github.com/ribalda/linux/commit/1623b648331d7f69c8a9f6b199e119f6c8ee61c6
>
> I let Laurent decide if we should squash with the previous patch or not.
>
> Thanks!
>
> >
> > #define uvc_trace_cont(flag, fmt, ...) \
> > do { \
> > if (uvc_trace_param & (flag)) \
> > pr_cont(fmt, ##__VA_ARGS__); \
> > } while (0)
> >
> > and change all the uses like:
> >
> > - if (uvc_trace_param & UVC_TRACE_PROBE)
> > - printk(KERN_CONT " <- SU %d", entity->id);
> > + uvc_trace_cont(UVC_TRACE_PROBE, " <- SU %d", entity->id);
> >
While I know the only uses of uvc_trace_cont are with UVC_TRACE_PROBE,
there are other existing uvc_trace(flag, ...) uses.
I think the uvc_trace_cont mechanism should require a flag and not
assume UVC_TRACE_PROBE so it's possible, even though currently unused,
for other uvc_trace calls to be continued.
$ git grep -Poh '\buvc_trace\(\w+' drivers/media | sort | uniq -c
1 uvc_trace(flag
6 uvc_trace(UVC_TRACE_CALLS
1 uvc_trace(UVC_TRACE_CAPTURE
2 uvc_trace(UVC_TRACE_CLOCK
15 uvc_trace(UVC_TRACE_CONTROL
42 uvc_trace(UVC_TRACE_DESCR
6 uvc_trace(UVC_TRACE_FORMAT
12 uvc_trace(UVC_TRACE_FRAME
7 uvc_trace(UVC_TRACE_PROBE
1 uvc_trace(UVC_TRACE_STATS
6 uvc_trace(UVC_TRACE_STATUS
4 uvc_trace(UVC_TRACE_SUSPEND
6 uvc_trace(UVC_TRACE_VIDEO
next prev parent reply other threads:[~2020-11-05 18:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 18:07 [PATCH v2 0/7] Show privacy_gpio as a v4l2_ctrl Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 1/7] media: uvcvideo: Use pr_cont() macro Ricardo Ribalda
2020-11-04 19:29 ` Joe Perches
2020-11-04 21:42 ` Laurent Pinchart
2020-11-04 21:51 ` Joe Perches
2020-11-04 22:31 ` Ricardo Ribalda
2020-11-04 23:00 ` Joe Perches
2020-11-04 23:01 ` Ricardo Ribalda
2020-11-04 23:59 ` Joe Perches
2020-11-05 9:50 ` Ricardo Ribalda
2020-11-05 18:58 ` Joe Perches [this message]
2020-11-05 19:52 ` Ricardo Ribalda
2020-11-04 21:42 ` Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 2/7] media: uvcvideo: Move guid to entity Ricardo Ribalda
2020-11-06 6:06 ` Laurent Pinchart
2020-11-06 8:45 ` Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 3/7] media: uvcvideo: Allow external entities Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 4/7] media: uvcvideo: Allow entities with no pads Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 5/7] media: uvcvideo: Entity defined get_info and get_cur Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 6/7] media: uvcvideo: Implement UVC_EXT_GPIO_UNIT Ricardo Ribalda
2020-11-04 18:07 ` [PATCH v2 7/7] media: uvcvideo: Add Privacy control based on EXT_GPIO Ricardo Ribalda
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=92c85080ad6e1ded9c15479efe79a7eb7b0c7ee2.camel@perches.com \
--to=joe@perches.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
/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
all inboxes | Powered by JetHome®