From: Greg KH <greg@kroah.com>
To: Mohamed Karaoui <moharaka@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: [RFC PATCH] kvm: replace spaces with a tab
Date: Thu, 16 May 2024 11:38:54 +0200 [thread overview]
Message-ID: <2024051614-fifteen-mutual-47df@gregkh> (raw)
In-Reply-To: <20240516093145.35644-1-moharaka@gmail.com>
On Thu, May 16, 2024 at 10:31:45AM +0100, Mohamed Karaoui wrote:
> Hi list,
>
> This is an attempt to get a feeling of sending a first patch. Please feel
> free to comment.
>
> I have few questions:
>
> - I have build this patch against the torvalds/linux.git. Does it matter
> which tree I use as long as it works on the maintainer tree?
>
> - In this particular case I checked the maintainer. It seems that its
> tree is something of 11 years old.
I suggest working on drivers/staging/ first for basic coding style fixes
like this, as they are encouraged there, but not necessarily in other
parts of the kerenel at all.
Good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-05-16 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 9:31 [RFC PATCH] kvm: replace spaces with a tab Mohamed Karaoui
2024-05-16 9:38 ` Greg KH [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=2024051614-fifteen-mutual-47df@gregkh \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=moharaka@gmail.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).