From: Deepak R Varma <drv@mailo.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: patches for staging:media drivers
Date: Sun, 6 Nov 2022 16:22:57 +0530 [thread overview]
Message-ID: <Y2eSCZJNWn6DzCUu@qemulion> (raw)
Greetings to all.
My name is Deepak R Varma and I was part of the recent Outreachy internship
round. I learned during this program that patches for the media drivers were
prohibited to be included in the Outreachy effort due to lack of bandwidth for
the maintainers to respond on those.
The Outreachy round is now over but I am continuing to work on code improvement
and changes. I would like to know if it is okay for me to now identify
opportunities in the media drivers and send patch proposal for your kind
consideration. I intend to send couple of Coccinelle identified code
improvements as patches.
Please let me know.
Thank you,
./drv
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-06 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 10:52 Deepak R Varma [this message]
2022-11-07 17:29 ` patches for staging:media drivers Neil Armstrong
2022-11-07 18:57 ` Deepak R Varma
2022-11-08 8:10 ` Dan Carpenter
2022-11-08 9:35 ` Hans Verkuil
2022-11-08 9:46 ` Dan Carpenter
2022-11-08 20:27 ` Andrew Lunn
2022-11-09 6:40 ` Deepak R Varma
2022-11-09 13:49 ` Andrew Lunn
2022-11-11 17:11 ` Deepak R Varma
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=Y2eSCZJNWn6DzCUu@qemulion \
--to=drv@mailo.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.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).