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 2/2] mm/cma: Use 'unsigned int' for cma_area_count type clarity
Date: Sat, 30 Dec 2023 16:06:06 +0000 [thread overview]
Message-ID: <CAO-+rPv0oC83qR0Hvb85mGWZXie8u0oMQkQNDw6H+7JSRUufdA@mail.gmail.com> (raw)
In-Reply-To: <ZY7oM8E5Mqqs5xHz@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Dear Matthew Wilcox,
I appreciate your feedback and understand the importance of respecting
coding style conventions. I apologize for any inconvenience caused.
As a newcomer to the Linux Kernel community, I am eager to contribute and
willing to learn from experienced members like yourself. If you could
provide some guidance on specific areas or types of code where
contributions are needed and welcomed, I would be grateful. I want to
ensure that my efforts align with the community's expectations.
Thank you for your understanding, and I look forward to your valuable
guidance.
Best regards,
Malkoot Khan
On Fri, Dec 29, 2023 at 3:39 PM Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Dec 29, 2023 at 03:32:38PM +0000, Malkoot Khan wrote:
> > Replace 'unsigned' with 'unsigned int' for the variable cma_area_count.
>
> Please don't run coding style tools over other people's code. Such
> changes are generally unwelcome.
>
--
*Regards:*
*Malkoot Khan*
[-- Attachment #2: Type: text/html, Size: 1555 bytes --]
next prev parent reply other threads:[~2023-12-30 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 15:32 [PATCH 1/2] mm/cma: Move opening brace to next line for coding style 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 [this message]
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
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-+rPv0oC83qR0Hvb85mGWZXie8u0oMQkQNDw6H+7JSRUufdA@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