From: Jonathan Bergh <bergh.jonathan@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: gregkh@linuxfoundation.org, 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 14:14:08 +0200 [thread overview]
Message-ID: <ZTPAkFCIjgWNBY2u@HP-ENVY-Notebook> (raw)
In-Reply-To: <acf1fade-7693-9332-03b1-626f4949f9ff@redhat.com>
On Sat, Oct 21, 2023 at 01:57:05PM +0200, Hans de Goede wrote:
> 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>
Hi Hans, thanks for the msg.
>
> Thank you for your patch, but please don't resend
> it every week.
Apologies. I dont remember when i sent the original but I was cleaning
up today and thought i would resend it. (I dont recall resending prior to
today (?) but if so, apologies).
> 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.
Yes, for sure, it was just a small thing.
Thanks Hans
br
Jonathan
prev parent reply other threads:[~2023-10-21 12:14 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
2023-10-21 12:14 ` Jonathan Bergh [this message]
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=ZTPAkFCIjgWNBY2u@HP-ENVY-Notebook \
--to=bergh.jonathan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.