From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
linux-media@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: [PATCH] media: i2c: adv748x: Fix unsafe macros
Date: Thu, 16 Jan 2020 22:28:29 +0000 [thread overview]
Message-ID: <c11f86b7-f304-2667-0d2a-3d30a965b700@ideasonboard.com> (raw)
In-Reply-To: <CAKwvOd=cA7E0MOtFfaQ5-+-v=+YNHYQPgMq6yS517PLLKn=Qpw@mail.gmail.com>
Hi Nick
On 16/01/2020 21:51, Nick Desaulniers wrote:
> On Thu, Jan 16, 2020 at 1:45 PM Gustavo A. R. Silva
> <gustavo@embeddedor.com> wrote:
>>
>> Hi!
>> Friendly ping:
>>
>> Who can take this?
>>
>> It's been almost three months now since I first sent this patch out.
>
> Kieran is listed as maintainer of:
> 998 F: drivers/media/i2c/adv748x/*
>
> but I'm guessing the tree would be Mauro's. It would be good if
> Kieran can review, then Mauro can pick up?
Already done on the 22nd October 2019:
https://lore.kernel.org/linux-media/22780ef3-514e-d013-1da8-9576780fde1c@ideasonboard.com/
Hans, Should this go through you?
Or are we just waiting for Mauro to pick it up?
--
Regards
--
Kieran
next prev parent reply other threads:[~2020-01-16 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 13:25 [PATCH] media: i2c: adv748x: Fix unsafe macros Gustavo A. R. Silva
2019-10-22 14:11 ` Kieran Bingham
2020-01-13 23:14 ` Nathan Chancellor
2020-01-16 21:45 ` Gustavo A. R. Silva
2020-01-16 21:51 ` Nick Desaulniers
2020-01-16 22:28 ` Kieran Bingham [this message]
2020-01-17 7:25 ` Hans Verkuil
2020-01-17 16:47 ` Nick Desaulniers
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=c11f86b7-f304-2667-0d2a-3d30a965b700@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dvyukov@google.com \
--cc=gustavo@embeddedor.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).