From: Hans Verkuil <hverkuil@xs4all.nl>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Deepak R Varma <mh12gx2825@gmail.com>
Cc: outreachy-kernel@googlegroups.com,
Steve Longerbeam <slongerbeam@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v5 1/2] staging: media: imx: remove commented code
Date: Tue, 27 Oct 2020 10:43:36 +0100 [thread overview]
Message-ID: <81449e51-957e-9478-5146-9c467248ccd3@xs4all.nl> (raw)
In-Reply-To: <20201026055631.GA779791@kroah.com>
On 26/10/2020 06:56, Greg Kroah-Hartman wrote:
> On Mon, Oct 26, 2020 at 09:30:17AM +0530, Deepak R Varma wrote:
>> On Fri, Oct 16, 2020 at 11:10:33PM +0530, Deepak R Varma wrote:
>>
>> Hello All,
>> Request for review / ack of this patch.
>
> Please never top-post :(
>
> The merge window only opened up a few hours ago, give maintainers time
> to get to patches (like 2 weeks now). Also remember, for the outreachy
> project, drivers/staging/media/ patches are not considered and take much
> longer to get reviewed and accepted, as the outreachy documentation
> states.
As media reviewer I've been very, very busy with other things for the past 3 weeks.
I plan to use most (all?) of next week to catch up on things.
Regards,
Hans
prev parent reply other threads:[~2020-10-27 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 17:40 [PATCH v5 1/2] staging: media: imx: remove commented code Deepak R Varma
2020-10-16 17:43 ` Steve Longerbeam
2020-10-16 17:46 ` [PATCH 2/2 v5] staging: media: imx: remove unnecessary variable use Deepak R Varma
2020-10-16 17:46 ` Steve Longerbeam
2020-10-26 4:02 ` Deepak R Varma
2020-10-26 4:00 ` [PATCH v5 1/2] staging: media: imx: remove commented code Deepak R Varma
2020-10-26 5:56 ` Greg Kroah-Hartman
2020-10-26 18:03 ` Deepak R Varma
2020-10-27 9:43 ` Hans Verkuil [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=81449e51-957e-9478-5146-9c467248ccd3@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mh12gx2825@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=slongerbeam@gmail.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).