From: Prasad Pandit <ppandit@redhat.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
gregkh@linuxfoundation.org, rjui@broadcom.com,
sbranden@broadcom.com, linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH v2] staging: bcm2835-audio: add terminating new line to Kconifg
Date: Wed, 13 Mar 2024 16:44:09 +0530 [thread overview]
Message-ID: <CAE8KmOzcD+__7xdC7tegbHO9HEP48s7=reA4j-tvqVDwzHr+8Q@mail.gmail.com> (raw)
In-Reply-To: <0a1aa580-50b2-4657-8308-94bffb194aea@moroto.mountain>
Hi,
On Wed, 13 Mar 2024 at 15:47, Dan Carpenter <dan.carpenter@linaro.org> wrote:
> Why does this make a difference? Is it just because it's annoying to
> cat a file that doesn't have a newline at the end?
* It's not just #PetPeeve. I'm trying to fix parsing errors reported
by the config-kernel tool[1], so that users can view all CONFIG
attributes without errors.
> I checked, and it's not a checkpatch warning. Perhaps it should be though.
> KTODO: make checkpatch.pl warn about files that don't end in a newline
* I'll take a look at checkpatch.pl.
> subject but he's on vacation... s/Kconifg/Kconfig/
> Just fix the subject and add a line to the commit message and I'll ack the patch.
* Okay, will send a revised patch.
Thank you.
---
- Prasad
[1] https://github.com/pjps/config-kernel
next prev parent reply other threads:[~2024-03-13 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 9:12 [PATCH v2] staging: bcm2835-audio: add terminating new line to Kconifg Prasad Pandit
2024-03-13 10:17 ` Dan Carpenter
2024-03-13 11:14 ` Prasad Pandit [this message]
2024-03-13 11:53 ` Dan Carpenter
2024-03-13 16:49 ` Prasad Pandit
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='CAE8KmOzcD+__7xdC7tegbHO9HEP48s7=reA4j-tvqVDwzHr+8Q@mail.gmail.com' \
--to=ppandit@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=pjp@fedoraproject.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).