From: Sakari Ailus <sakari.ailus@iki.fi>
To: dev.dragon@bk.ru
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: media: atomisp: pci: fixed a curly bracket coding style issue.
Date: Tue, 13 Apr 2021 13:23:22 +0300 [thread overview]
Message-ID: <20210413102322.GL3@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <20210411134840.7184-1-dev.dragon@bk.ru>
On Sun, Apr 11, 2021 at 04:48:41PM +0300, dev.dragon@bk.ru wrote:
> From: Dmitrii Wolf <dev.dragon@bk.ru>
>
> Fixed a coding style issue.
>
> Signed-off-by: Dmitrii Wolf <dev.dragon@bk.ru>
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Sakari Ailus
next prev parent reply other threads:[~2021-04-13 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 13:48 [PATCH] Staging: media: atomisp: pci: fixed a curly bracket coding style issue dev.dragon
2021-04-13 10:23 ` Sakari Ailus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-10 19:16 dev.dragon
2021-04-30 7:54 ` Sakari Ailus
2021-04-30 7:55 ` Sakari Ailus
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=20210413102322.GL3@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=dev.dragon@bk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.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;
as well as URLs for NNTP newsgroup(s).