From: Bagas Sanjaya <bagasdotme@gmail.com>
To: angus gardner <angusg778@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: Removed unnecessary parenthesis around conditions to comply with the checkpatch coding style.
Date: Fri, 15 Sep 2023 14:56:38 +0700 [thread overview]
Message-ID: <ZQQONo8biMWlCiG3@debian.me> (raw)
In-Reply-To: <CAC5tM5u8L50fAhReAmP0dqexSmv-PdZJKa_ES2hxZMp41MJjGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Fri, Sep 15, 2023 at 11:58:47AM +1000, angus gardner wrote:
> Thanks for the feedback Bagas,
>
> "Then checkpatch is wrong, " lol
>
> Ill double check my SoB.
>
tl;dr:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
Also, don't send HTML emails as mailing lists reject them away.
Last but not least, this is the third time you do parentheses fixup, for
which Greg's bot said:
> You sent a patch that has been sent multiple times in the past few
> days, and is identical to ones that has been recently rejected.
> Please always look at the mailing list traffic to determine if you are
> duplicating other people's work.
Again, read all Documentation/process/*.rst docs so that you won't make
mistakes again as kernel developer.
Bye!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-09-15 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 1:02 [PATCH] staging: fbtft: Removed unnecessary parenthesis around conditions to comply with the checkpatch coding style Angus Gardner
2023-09-13 1:32 ` Bagas Sanjaya
[not found] ` <CAC5tM5u8L50fAhReAmP0dqexSmv-PdZJKa_ES2hxZMp41MJjGQ@mail.gmail.com>
2023-09-15 7:56 ` Bagas Sanjaya [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=ZQQONo8biMWlCiG3@debian.me \
--to=bagasdotme@gmail.com \
--cc=angusg778@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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 NNTP newsgroup(s).