From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Aaron Lawrence <t4rmin@zohomail.com>, linux-staging@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: rtl8192e: fixed multiple coding style issues
Date: Sat, 22 Oct 2022 07:16:24 +0200 [thread overview]
Message-ID: <ee426ce3-b336-1b9d-32a1-55e184028f8a@gmail.com> (raw)
In-Reply-To: <be839b05d799ff8e62fc2f79e6f0aaec81a8cd19.camel@zohomail.com>
On 10/22/22 07:05, Aaron Lawrence wrote:
Hi,
please do not attach patches to the email. Make the email the patch.
Have a look at the examples:
https://lore.kernel.org/linux-staging/
> Subject: [PATCH] Staging: rtl8192e: fixed multiple coding style issues
>
> Fixed multiple coding style issues on multiple files
> according to the checkpatchscript.
Please do one type of a change at a time and not multiple changes. Look
for examples in the above link or in the kernel.
Thanks
Bye Philipp
next prev parent reply other threads:[~2022-10-22 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 5:05 [PATCH] Staging: rtl8192e: fixed multiple coding style issues Aaron Lawrence
2022-10-22 5:16 ` Philipp Hortmann [this message]
2022-10-22 5:58 ` Greg KH
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=ee426ce3-b336-1b9d-32a1-55e184028f8a@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=t4rmin@zohomail.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