Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Ki-Seok Jo <kiseok.jo@irondevice.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: Re: FW: [PATCH v2 2/3] ASoC: dt-bindings: irondevice,sma1307: Add initial DT binding
Date: Wed, 11 Sep 2024 19:26:48 +0100	[thread overview]
Message-ID: <20240911-blaming-scant-9537304c2221@spud> (raw)
In-Reply-To: <SE1P216MB2348C5726B70913B57D8C67C8C9B2@SE1P216MB2348.KORP216.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 2305 bytes --]

On Wed, Sep 11, 2024 at 01:16:01AM +0000, Ki-Seok Jo wrote:
> > >
> > > I have no intention of opposing the content. I am asking again because I
> > didn't receive any warnings when I did the following, and I suspect I might
> > have done something wrong.
> > >
> > >
> > > ./scripts/checkpatch.pl
> > > Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml
> > >
> > > total: 0 errors, 0 warnings, 54 lines checked
> > >
> > > Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml has no
> > obvious style problems and is ready for submission.
> > >
> > > I was under the impression that this only applied to patched files as
> > described above. It turns out it can also be used with patch files. Thank you
> > for the useful information!
> > >
> > 
> > That's not how you run checkpatch. You run it on the patch. Please read
> > submitting-patches document. It explains everything.
> > 
> > Best regards,
> > Krzysztof
> 
> 
> Hi,
> 
> I am in the process of carefully incorporating your feedback and making the necessary revisions.
> 
> May I kindly ask you a question, if it's not too much trouble?
> When running checkpatch, what would be the best way to address the following warning?
> 
> WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> #21:
>  create mode 100644 Documentation/devicetree/bindings/sound/irondevice,sma1307.yaml
> 
> In this case, would it be better for me to add a line break in the patch file, or should I leave it as is?

Normally I would say you can ignore this, and that checkpatch doesn't
usually complain about the actually git output in here - but I think
checkpatch "broke" because you did not provide any commit message body
at all, so it starting parsing the git output instead. You need to write
a body!

> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> #65:
> new file mode 100644
> 
> If the warning is appearing because it's a new file, is it something that can be safely ignored, or should I make changes to the MAINTAINERS file?
> 
> Thank you for your feedback. I am learning a lot of new things!

Usually for bindings, which have maintainers listed in them, you can
skip adding a MAINTAINERS entry.

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-09-11 18:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  5:44 [PATCH v2 0/3] Add a driver for the Iron Device SMA1307 Amp Kiseok Jo
2024-09-03  5:44 ` [PATCH v2 1/3] ASoC: sma1307: Add driver for Iron Device SMA1307 Kiseok Jo
2024-09-03  6:57   ` Krzysztof Kozlowski
2024-09-03  6:58     ` Krzysztof Kozlowski
2024-09-03  7:57       ` Ki-Seok Jo
2024-09-03  8:15         ` Krzysztof Kozlowski
2024-09-03  8:33     ` Ki-Seok Jo
2024-09-03  8:51       ` Krzysztof Kozlowski
2024-09-03 15:57   ` kernel test robot
2024-09-03 18:12   ` Mark Brown
2024-09-12  8:35     ` Ki-Seok Jo
2024-09-12 11:23       ` Mark Brown
2024-09-03  5:44 ` [PATCH v2 2/3] ASoC: dt-bindings: irondevice,sma1307: Add initial DT binding Kiseok Jo
2024-09-03  6:49   ` Krzysztof Kozlowski
2024-09-03  8:39     ` Ki-Seok Jo
2024-09-03  8:55       ` Krzysztof Kozlowski
2024-09-03  9:08         ` Ki-Seok Jo
2024-09-03  9:14           ` Krzysztof Kozlowski
2024-09-03 13:39             ` Mark Brown
2024-09-11  1:16             ` FW: " Ki-Seok Jo
2024-09-11 18:26               ` Conor Dooley [this message]
2024-09-12  0:25                 ` Ki-Seok Jo
2024-09-03  5:44 ` [PATCH v2 3/3] doc: ABI: testing: sma1307: Add support for SMA1307 Kiseok Jo

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=20240911-blaming-scant-9537304c2221@spud \
    --to=conor@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=kiseok.jo@irondevice.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.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