From: Hans de Goede <hdegoede@redhat.com>
To: Jonathan Bergh <bergh.jonathan@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] staging: media: atomisp: Removed duplicate comment and fixed comment format
Date: Sat, 21 Oct 2023 13:57:05 +0200 [thread overview]
Message-ID: <acf1fade-7693-9332-03b1-626f4949f9ff@redhat.com> (raw)
In-Reply-To: <20231021110058.85013-1-bergh.jonathan@gmail.com>
Hi Jonathan,
On 10/21/23 13:00, Jonathan Bergh wrote:
> Fixed the following issues:
> * Removed a duplicate comment
> * Fixed up minor comment format issue
>
> Signed-off-by: Jonathan Bergh <bergh.jonathan@gmail.com>
Thank you for your patch, but please don't resend
it every week.
I did see the original patch and it looks fine but
I have not had any time to work in atomisp support
recently and this does not seem like something
which needs to get merged urgently.
I'll pick this up next time I have time to do
a bunch of atomisp work.
Regards,
Hans
> ---
> drivers/staging/media/atomisp/i2c/gc2235.h | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/i2c/gc2235.h b/drivers/staging/media/atomisp/i2c/gc2235.h
> index 55ea422291ba..ade28950db73 100644
> --- a/drivers/staging/media/atomisp/i2c/gc2235.h
> +++ b/drivers/staging/media/atomisp/i2c/gc2235.h
> @@ -74,9 +74,6 @@
> #define GC2235_COARSE_INTG_TIME_MIN 1
> #define GC2235_COARSE_INTG_TIME_MAX_MARGIN 6
>
> -/*
> - * GC2235 System control registers
> - */
> /*
> * GC2235 System control registers
> */
> @@ -167,7 +164,7 @@ enum gc2235_tok_type {
> GC2235_TOK_MASK = 0xfff0
> };
>
> -/**
> +/*
> * struct gc2235_reg - MI sensor register format
> * @type: type of the register
> * @reg: 8-bit offset to register
next prev parent reply other threads:[~2023-10-21 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 11:00 [PATCH RESEND] staging: media: atomisp: Removed duplicate comment and fixed comment format Jonathan Bergh
2023-10-21 11:57 ` Hans de Goede [this message]
2023-10-21 12:14 ` Jonathan Bergh
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=acf1fade-7693-9332-03b1-626f4949f9ff@redhat.com \
--to=hdegoede@redhat.com \
--cc=bergh.jonathan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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