All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prashant Rahul" <prashantrahul23@gmail.com>
To: "Dan Carpenter" <error27@gmail.com>
Cc: "Prashant Rahul" <prashantrahul23@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Shuah Khan" <shuah@kernel.org>, <linux-staging@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] staging: octeon: Improve initialization error handling
Date: Mon, 29 Jun 2026 13:55:46 +0530	[thread overview]
Message-ID: <DJLE1OGDMMV0.1TSDJRDW4Z547@gmail.com> (raw)
In-Reply-To: <akIdyUhcH6O-Iczx@stanley.mountain>

On Mon Jun 29, 2026 at 12:54 PM IST, Dan Carpenter wrote:

> You need to say when you haven't tested your code.

will do, thank you!

> You need to say when you're using AI to write patches.  There is
> a format for it.
> Documentation/process/coding-assistants.rst

Thank you for pointing it out, however I have not used any AI assistant
for this patch series. I used Harper, an offline grammar checker, to
help me write the emails, do I need to specify that? Other than that I used
basic tools like an editor, make, git etc.

  reply	other threads:[~2026-06-29  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28  7:01 [PATCH 0/4] staging: octeon: Improve initialization error handling Prashant Rahul
2026-06-28  7:01 ` [PATCH 1/4] staging: octeon: factor out device removal into a helper Prashant Rahul
2026-06-29  7:25   ` Dan Carpenter
2026-06-29  7:45   ` Dan Carpenter
2026-06-28  7:01 ` [PATCH 2/4] staging: octeon: Propagate rx initialization failures Prashant Rahul
2026-06-28  7:01 ` [PATCH 3/4] staging: octeon: Propagate tx " Prashant Rahul
2026-06-28  7:01 ` [PATCH 4/4] staging: octeon: handle rx/tx initialization failures in probe Prashant Rahul
2026-06-29  7:44   ` Dan Carpenter
2026-06-29  7:24 ` [PATCH 0/4] staging: octeon: Improve initialization error handling Dan Carpenter
2026-06-29  8:25   ` Prashant Rahul [this message]
2026-06-29  8:45     ` 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=DJLE1OGDMMV0.1TSDJRDW4Z547@gmail.com \
    --to=prashantrahul23@gmail.com \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.