mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Omer PALA <palaomer100@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
	Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
	Vaibhav Agarwal <vaibhav.sr@gmail.com>,
	Mark Greer <mgreer@animalcreek.com>,
	Viresh Kumar <vireshk@kernel.org>,
	Rui Miguel Silva <rmfrfs@gmail.com>,
	Bryan O'Donoghue <pure.logic@nexus-software.ie>,
	David Lin <dtwlin@gmail.com>,
	"moderated list:GREYBUS SUBSYSTEM" <greybus-dev@lists.linaro.org>,
	"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: greybus: change mutexes to guard macros
Date: Sun, 20 Sep 2026 15:22:08 +0200	[thread overview]
Message-ID: <ea6cf31e-0acd-4248-9359-5864bf8f6f94@kernel.org> (raw)
In-Reply-To: <DLK2TDB5QIUL.1X53SKJTROLDK@gmail.com>

On 20/09/2026 12:37, Omer PALA wrote:
> Hi Greg,
> 
> I thought someone (not you) can allow this.

So you received feedback from Greg, but tried on different part, hoping
this time it will get accepted?

This looks similar to you previous approaches, e.g. for DT bindings,
where you received comments and repeated the same thing immediately.
Three or four time.

> 
> I want to contribute kernel but i dont know what should i do.

I suggest spend some time to actually read the archives when people
point it.


> 
> I wrote 3 devicetree schemas, 2 performance fixes, 2 mutex/spinlock
> fixes and 1 syntax fix.
> 
> All of my work got NAK.

One was pure AI slop, so what did you expect exactly? In all channels,
fediverse, some technological news, open source projects complain about
sent slop, they reject it and treat it as one of biggest time wasting
thing contributor could do. It is not like we hide it, right? Actually
opposite, everywhere we scream - don't send vibe coded stuff. And for
learning or beginning this is even unacceptable waste of your time,
because you will learn nothing. I was raising it for GSoC for example
more than once and it is documented in their rules.

> 
> Can you explain me what should i do?

One idea would be to read more before you actually contribute.


Best regards,
Krzysztof

  parent reply	other threads:[~2026-09-20 13:22 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
2026-09-20 12:37     ` Greg Kroah-Hartman
2026-09-20 13:22     ` Krzysztof Kozlowski [this message]
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=ea6cf31e-0acd-4248-9359-5864bf8f6f94@kernel.org \
    --to=krzk@kernel.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®