From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linuxarm@huawei.com, mauro.chehab@huawei.com,
Jonathan Corbet <corbet@lwn.net>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] media: add a subsystem profile documentation
Date: Mon, 1 Mar 2021 14:47:41 +0100 [thread overview]
Message-ID: <20210301144741.11a5751b@coco.lan> (raw)
In-Reply-To: <e757851a-91a1-225b-fa6e-3c7d44a6cc5c@xs4all.nl>
Em Mon, 1 Mar 2021 13:27:39 +0100
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> Hi Mauro,
>
Thanks for your review. I'm addressing the points on a v5.
Yet, there's one that, IMHO, we should elaborate more, if we add it to the
doc:
> > +Provided that your patch is at https://patchwork.linuxtv.org, it should
> > +be sooner or later handled, so you don't need to re-submit a patch.
> > +
> > +Except for bug fixes, we don't usually add new patches to the development
> > +tree between -rc6 and the next -rc1.
> > +
> > +Please notice that the media subsystem is a high traffic one, so it
> > +could take a while for us to be able to review your patches. Feel free
> > +to ping if you don't get a feedback in a couple of weeks or to ask
> > +other developers to publicly add Reviewed-by and, more importantly,
> > +Tested-by tags.
>
> What I have noticed is that sometimes important bug fixes are missed due
> to the high traffic volume. I would like to see something along the lines of:
>
> "If important bug fixes are not reviewed or picked up within a week of posting,
> then do not hesitate to ping."
I see your point, but "important" is relative ;-) I mean, a bug
is almost always important for the one reporting it. It doesn't
necessarily means that such bug is visible by others or if the
subsystem's core has a serious bug.
IMO, if we add a paragraph like that, we should better explain what
"important" means.
Thanks,
Mauro
next prev parent reply other threads:[~2021-03-01 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 11:46 [PATCH v4] media: add a subsystem profile documentation Mauro Carvalho Chehab
2021-03-01 12:27 ` Hans Verkuil
2021-03-01 13:47 ` Mauro Carvalho Chehab [this message]
2021-03-01 14:12 ` Hans Verkuil
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=20210301144741.11a5751b@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=hverkuil@xs4all.nl \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lukas.bulwahn@gmail.com \
--cc=mauro.chehab@huawei.com \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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