From: Bradley Morgan <brads@mainlining.org>
To: palaomer100@gmail.com
Cc: dtwlin@gmail.com, elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, hvaibhav.linux@gmail.com,
johan@kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, mgreer@animalcreek.com,
pure.logic@nexus-software.ie, rmfrfs@gmail.com,
vaibhav.sr@gmail.com, vireshk@kernel.org
Subject: Re: [PATCH] staging: greybus: change mutexes to guard macros
Date: Sun, 20 Sep 2026 12:59:34 +0100 [thread overview]
Message-ID: <33F62319-50BA-45F8-BEDA-75BC4AFBAC93@mainlining.org> (raw)
In-Reply-To: <DLK2TDB5QIUL.1X53SKJTROLDK@gmail.com>
On 20 September 2026 11:37:00 BST, Omer PALA <palaomer100@gmail.com> wrote:
>Hi Greg,
>
>I thought someone (not you) can allow this.
>
>I want to contribute kernel but i dont know what should i do.
>
>I wrote 3 devicetree schemas, 2 performance fixes, 2 mutex/spinlock
>fixes and 1 syntax fix.
>
>All of my work got NAK.
>
>Can you explain me what should i do?
>
>Best Regards,
>Omer PALA
Hi, I don't tend to jump into staging threads, because well I don't do
staging and all that, but I'm sure I can help you here.
From me looking in archives, you tend to use AI tools, which isn't allowed
in staging as of right now.
Staging is a learners playground, not a AI bot bug report thing.
If you need any help you can contact me off list any time you need it, I
do need to start mentoring people....
>
>
--- Thanks!
"I'm not a very positive person" - Linus torvalds
next prev parent reply other threads:[~2026-09-20 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 9:40 Omer PALA
2026-09-20 10:11 ` Greg Kroah-Hartman
2026-09-20 10:37 ` Omer PALA
2026-09-20 11:59 ` Bradley Morgan [this message]
2026-09-20 12:37 ` Greg Kroah-Hartman
2026-09-20 13:22 ` Krzysztof Kozlowski
2026-09-20 13:26 ` Krzysztof Kozlowski
2026-09-20 18:29 ` Ömer PALA
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=33F62319-50BA-45F8-BEDA-75BC4AFBAC93@mainlining.org \
--to=brads@mainlining.org \
--cc=dtwlin@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=hvaibhav.linux@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mgreer@animalcreek.com \
--cc=palaomer100@gmail.com \
--cc=pure.logic@nexus-software.ie \
--cc=rmfrfs@gmail.com \
--cc=vaibhav.sr@gmail.com \
--cc=vireshk@kernel.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
all inboxes | Powered by JetHome®