mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
To: krzk@kernel.org
Cc: alim.akhtar@samsung.com, bhelgaas@google.com,
	jingoohan1@gmail.com, kwilczynski@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, lpieralisi@kernel.org,
	mani@kernel.org, peter.griffin@linaro.org, robh@kernel.org,
	sreekuttan2156239@gmail.com
Subject: Re: [PATCH v8] PCI: exynos: Handle PCIe PHY initialization errors
Date: Thu, 19 Nov 2026 14:22:51 +0000	[thread overview]
Message-ID: <20261119142251.2665-1-sreekuttan2156239@gmail.com> (raw)
In-Reply-To: <0a3b7886-3800-42ee-8e22-80944114dfcf@kernel.org>

Hi Krzysztof,

Thank you for your feedback. I would like to clarify a few things regarding the patches 
and the concerns you raised.

The code is not entirely AI-written, as you claim. The reason I sent multiple patches on 
the same day is that I was working on them over time and submitting them as they were ready. 
They were not all written and sent at once. There was a time gap between the submissions, so 
please don't assume that I was blindly sending random patches just to get past the review process.

Regarding the v2 to v9 revisions, I admit that I blindly trusted your Shashiko reviews. I submitted 
the patches on my holiday, assuming that Shashiko was properly trained on the latest Linux kernel 
source code. I also assumed that, since the PCI subsystem uses Shashiko for patch reviews, its 
feedback would be reliable enough to trust.

If Shashiko repeatedly reports issues that are incorrect or misleading, why is it being used as a 
review tool in the first place? Isn't relying on such feedback equally problematic? I trusted its 
suggestions because I assumed that the review system was reliable and that its feedback had been 
properly validated.

Manivannan Sadhashivam also advised me not to blindly trust automated review tools. However, he 
explained his concerns constructively and helped me understand where I was going wrong. 
He understood that I had trusted Shashiko's feedback in good faith. I appreciate that kind of 
review because it helps contributors learn and improve rather than simply questioning their 
understanding or dismissing their work as AI-generated slop.

I'm not claiming that my patches are perfect, and I'm willing to take responsibility for genuine 
mistakes. But dismissing the work as "100% AI-written slop" simply because I submitted multiple 
revisions is unfair. Humans can also submit multiple patches in a single day. That alone does not 
prove that the code is AI-generated or that the author doesn't understand it.

I understand your concerns about code quality, and I will take greater care to verify every review 
comment instead of blindly trusting automated feedback in the future.

I respect your experience and feedback, and I am willing to learn from genuine technical criticism. 
My intention has always been to contribute quality code to the Linux kernel and improve through the 
review process. I hope you can understand my perspective as well.

Best regards, 
Sreeraj

  reply	other threads:[~2026-11-19 14:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 13:10 [PATCH] PCI: exynos: Handle " Sreeraj S Kurup
2026-10-29 17:54 ` [PATCH v2] PCI: exynos: Handle PCIe " Sreeraj S Kurup
2026-10-30 15:17 ` [PATCH v3] " Sreeraj S Kurup
2026-10-30 16:36 ` [PATCH v4] " Sreeraj S Kurup
2026-10-30 17:23 ` [PATCH v5] " Sreeraj S Kurup
2026-10-30 18:09 ` [PATCH v6] " Sreeraj S Kurup
2026-10-31  7:01 ` [PATCH v7] " Sreeraj S Kurup
2026-10-31  7:35 ` [PATCH v8] " Sreeraj S Kurup
2026-11-19 12:10   ` Krzysztof Kozlowski
2026-11-19 14:22     ` Sreeraj S Kurup [this message]
2026-10-31  9:49 ` [PATCH v9] " Sreeraj S Kurup
2026-11-19 10:52   ` Manivannan Sadhasivam

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=20261119142251.2665-1-sreekuttan2156239@gmail.com \
    --to=sreekuttan2156239@gmail.com \
    --cc=alim.akhtar@samsung.com \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=krzk@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@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®