From: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
To: dan.carpenter@linaro.org
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, azpijr@gmail.com
Subject: Re: [PATCH] staging: greybus: camera: add comment for mutex
Date: Wed, 25 Feb 2026 12:31:47 +0100 [thread overview]
Message-ID: <20260225113150.109829-1-azpijr@gmail.com> (raw)
In-Reply-To: <DAN_CARPENTERS_MESSAGE_ID>
Thank you for the honest feedback. I'm a new contributor and I was
trying to resolve the checkpatch.pl CHECKs to get familiar with the
process, but I see now that vague documentation can be worse than none
at all.
I'll withdraw this patch. Since I'm looking to make my first meaningful
contribution to staging, do you have any suggestions on what types of
issues in Greybus are actually helpful for a beginner to tackle?
regards, jose
next parent reply other threads:[~2026-02-25 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DAN_CARPENTERS_MESSAGE_ID>
2026-02-25 11:31 ` Jose A. Perez de Azpillaga [this message]
2026-02-25 11:05 [PATCH] staging: greybus: camera: add comment for mutex Jose A. Perez de Azpillaga
2026-02-25 11:18 ` Dan Carpenter
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=20260225113150.109829-1-azpijr@gmail.com \
--to=azpijr@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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