public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Scott Mayhew <smayhew@redhat.com>,
	Jeff Layton <jlayton@kernel.org>,
	kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH 0/2] Align guest dependencies with their corresponding workflows
Date: Fri, 25 Jul 2025 15:45:04 +0200	[thread overview]
Message-ID: <ebbcbe3c-0ebe-4cb0-86cf-345e8f3fb41f@kernel.org> (raw)
In-Reply-To: <CAB=NE6WtUTSW__GMN5FyJC-99bu1LpfNkHyHzmPAd+RSdLf2kg@mail.gmail.com>



On 25/07/2025 10.15, Luis Chamberlain wrote:
> On Fri, Jul 25, 2025 at 1:09 AM Daniel Gomez <da.gomez@kernel.org> wrote:
> 
>> So, I was looking into having something like checkpatch some time ago. Now, with
>> this generative AI there's no reason to wait. So I think it's a good idea to
>> go with that. But it's missing b4 integration. "b4 prep --check" for the kernel
>> runs checkpatch like this [1]:
> 
> Sounds good. This patch was just in another series I have but if its
> useful I figured I'd send it out. So no worries. But if you're going
> to extend it with more stuff, if you can pick it up and extend it
> that'd be neat as then I can just remove that from my future queue of
> patches to post. I gather at this point this is just going to be
> normal for us to use these tools to grow kdevops and so the sooner we
> have sanity checks the better. Could you pick up this patch and amend
> it with the ideas you have too? Then I'll just carry it locally until
> you push it out and I can then ignore this patch later?

Pushed it to my kdevops fork:

https://github.com/dkruces/kdevops/tree/b4/checkpatch

I'll play soon with Claude Code to run local checks for patches and see how far
we can go.

> 
>   Luis














      reply	other threads:[~2025-07-25 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 18:34 [PATCH 0/2] Align guest dependencies with their corresponding workflows Daniel Gomez
2025-07-24 18:34 ` [PATCH 1/2] kconfig: add workflow dependencies for SMBD and KRB5 services Daniel Gomez
2025-07-24 18:34 ` [PATCH 2/2] kconfig: add workflow dependencies for NFSD and iSCSI services Daniel Gomez
2025-07-24 19:44 ` [PATCH 0/2] Align guest dependencies with their corresponding workflows Chuck Lever
2025-07-24 19:48 ` Luis Chamberlain
2025-07-25  7:33   ` Daniel Gomez
2025-07-25  7:39     ` Luis Chamberlain
2025-07-25  8:09       ` Daniel Gomez
2025-07-25  8:15         ` Luis Chamberlain
2025-07-25 13:45           ` Daniel Gomez [this message]

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=ebbcbe3c-0ebe-4cb0-86cf-345e8f3fb41f@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=da.gomez@samsung.com \
    --cc=jlayton@kernel.org \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@kernel.org \
    --cc=smayhew@redhat.com \
    /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