From: Julia Lawall <julia.lawall@inria.fr>
To: Mitali Borkar <mitaliborkar810@gmail.com>
Cc: clabbe@baylibre.com, mchehab@kernel.org,
gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com, mitali_s@me.iitr.ac.in
Subject: Re: [Outreachy kernel] [PATCH v2 1/2] media: zoran: add spaces around '<<'
Date: Fri, 9 Apr 2021 22:40:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2104092239170.23056@hadrien> (raw)
In-Reply-To: <YHCgksbiLv0pFF2F@kali>
On Sat, 10 Apr 2021, Mitali Borkar wrote:
> No changes required in this patch.
> In v1:- Added spaces around '<<' operator to improve readability and meet linux kernel coding
> style
The text above would go in the git history. "No changes required in this
patch." doesn't make sense in that context. If you want to say something
that relates to the history of the submitted patches, then that should be
under the ---. The text there will disappear when the patch is applied.
julia
>
> Signed-off-by: Mitali Borkar <mitaliborkar810@gmail.com>
> ---
>
> Changes from v1:- No changes required in this patch. Below is the git
> diff of v1.
>
> drivers/staging/media/zoran/zr36057.h | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/media/zoran/zr36057.h b/drivers/staging/media/zoran/zr36057.h
> index 71b651add35a..a2a75fd9f535 100644
> --- a/drivers/staging/media/zoran/zr36057.h
> +++ b/drivers/staging/media/zoran/zr36057.h
> @@ -30,13 +30,13 @@
> #define ZR36057_VFESPFR_HOR_DCM 14
> #define ZR36057_VFESPFR_VER_DCM 8
> #define ZR36057_VFESPFR_DISP_MODE 6
> -#define ZR36057_VFESPFR_YUV422 (0<<3)
> -#define ZR36057_VFESPFR_RGB888 (1<<3)
> -#define ZR36057_VFESPFR_RGB565 (2<<3)
> -#define ZR36057_VFESPFR_RGB555 (3<<3)
> -#define ZR36057_VFESPFR_ERR_DIF (1<<2)
> -#define ZR36057_VFESPFR_PACK24 (1<<1)
> -#define ZR36057_VFESPFR_LITTLE_ENDIAN (1<<0)
> +#define ZR36057_VFESPFR_YUV422 (0 << 3)
> +#define ZR36057_VFESPFR_RGB888 (1 << 3)
> +#define ZR36057_VFESPFR_RGB565 (2 << 3)
> +#define ZR36057_VFESPFR_RGB555 (3 << 3)
> +#define ZR36057_VFESPFR_ERR_DIF (1 << 2)
> +#define ZR36057_VFESPFR_PACK24 (1 << 1)
> +#define ZR36057_VFESPFR_LITTLE_ENDIAN (1 << 0)
>
> #define ZR36057_VDTR 0x00c /* Video Display "Top" Register */
>
> --
> 2.30.2
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/YHCgksbiLv0pFF2F%40kali.
>
next prev parent reply other threads:[~2021-04-09 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 18:44 [PATCH v2 1/2] media: zoran: add spaces around '<<' Mitali Borkar
2021-04-09 20:40 ` Julia Lawall [this message]
2021-04-09 22:03 ` [Outreachy kernel] " Mitali Borkar
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=alpine.DEB.2.22.394.2104092239170.23056@hadrien \
--to=julia.lawall@inria.fr \
--cc=clabbe@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mitali_s@me.iitr.ac.in \
--cc=mitaliborkar810@gmail.com \
--cc=outreachy-kernel@googlegroups.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