From: malkoot khan <engr.mkhan1990@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/cma: Move opening brace to next line for coding style
Date: Sat, 30 Dec 2023 16:00:28 +0000 [thread overview]
Message-ID: <CAO-+rPtOd-c8_=noWC-+2GHNcCdVQHAGWTXu4kj23bw_wGt3rQ@mail.gmail.com> (raw)
In-Reply-To: <ZY7oAR7l4HYxJ8y3@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
Dear Matthew Wilcox,
I hope this email finds you well. My name is Malkoot Khan, and I am a new
member of the Linux Kernel contributor community. I am reaching out to
express my eagerness to contribute to the kernel and to kindly request your
guidance and assistance in this endeavor.
In my initial attempt to contribute, I encountered a situation where the
./scripts/checkpatch.pl tool flagged an error, specifically suggesting the
relocation of braces to the next line. Following this advice resolved the
issue, but I want to ensure that my approach aligns with the community's
best practices.
I would appreciate it if you could review my correction and provide any
insights or corrections if needed. I am keen on learning and adhering to
the community's coding standards.
Additionally, I recently watched one of your maintainer lectures on YouTube
("https://www.youtube.com/watch?v=LLBrBBImJt4"), which was highly
informative and inspiring. It played a significant role in guiding me
through the correction process.
Thank you for your time and consideration. I look forward to your valuable
guidance as I embark on my journey of contributing to the Linux Kernel.
Best regards,
Malkoot Khan
On Fri, Dec 29, 2023 at 3:38 PM Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Dec 29, 2023 at 03:32:37PM +0000, Malkoot Khan wrote:
> > Move the opening brace of a function definition 'cma_for_each_area'
> > to the next line which resolved the error
>
> What error? This seems like the _wrong_ coding style to me.
>
> > Signed-off-by: Malkoot Khan <engr.mkhan1990@gmail.com>
> > ---
> > mm/cma.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/mm/cma.c b/mm/cma.c
> > index 2b2494fd6b59..01ccd26e8bc2 100644
> > --- a/mm/cma.c
> > +++ b/mm/cma.c
> > @@ -579,6 +579,7 @@ bool cma_release(struct cma *cma, const struct page
> *pages,
> > }
> >
> > int cma_for_each_area(int (*it)(struct cma *cma, void *data), void
> *data)
> > +
> > {
> > int i;
> >
> > --
> > 2.34.1
> >
> >
>
--
*Regards:*
*Malkoot Khan*
[-- Attachment #2: Type: text/html, Size: 2959 bytes --]
prev parent reply other threads:[~2023-12-30 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 15:32 Malkoot Khan
2023-12-29 15:32 ` [PATCH 2/2] mm/cma: Use 'unsigned int' for cma_area_count type clarity Malkoot Khan
2023-12-29 15:39 ` Matthew Wilcox
2023-12-30 16:06 ` malkoot khan
2023-12-29 15:38 ` [PATCH 1/2] mm/cma: Move opening brace to next line for coding style Matthew Wilcox
2023-12-30 16:00 ` malkoot khan [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='CAO-+rPtOd-c8_=noWC-+2GHNcCdVQHAGWTXu4kj23bw_wGt3rQ@mail.gmail.com' \
--to=engr.mkhan1990@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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