From: Daniel Watson <ozzloy@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: screening patch here before sending to devs
Date: Tue, 28 Mar 2023 00:47:26 -0700 [thread overview]
Message-ID: <ZCKbjmrrPc8C+NyD@trent-reznor> (raw)
In-Reply-To: <CAKXUXMyi4g78KEPda7YVMdo1D=DaF_8YkPfkxNbFgC6TJj9fPQ@mail.gmail.com>
On Tue, Mar 28, 2023 at 09:03:17AM +0200, Lukas Bulwahn wrote:
> Hi Daniel,
Hi! thanks for pre-reviewing!
>
> Sometimes patches show up multiple times in lore.kernel.org archives,
> as some mailing list add further footers, so the same content sent is
> recorded slightly differently in the archives, leading to multiple
> copies. This is not considered double posting, though, as it is
> default to send a patch to multiple mailing lists, e.g., specific
> subsystem mailing list and the general linux-kernel mailing list. As
> long as the message has the same Message-ID, it is clear they were
> sent with one "git send-email" invocation.
cool. must be something wrong with gmail then. it's showing twice in my
gmail. i'm not using git send-email, i'm using mutt configured to send
through gmail.
> Usually "{" would be written out as "opening brackets" or as "curly
> brackets", just having a special character, like "{", is not seen
> often in commit message subject lines.
noted, i've changed that.
>
> Usually, consistency beats style. So, check if this pattern appears in
> any files in drivers/staging/rtl8723bs/ and its subdirectories and try
> to fix all instances within that directory with one patch.
earlier in the same file, the curly bracket appears on the opening line,
except for functions.
> Other than that, it looks like a good newcomer's first submission patch.
that's great! i've sent it in with the changes.
i would like to work on my laptop battery's charge threshold. it can be
changed in the bios, but not while running. there's a project for doing
this on some thinkpads, but not the framework laptop. any pointers for
where to get more info about this would be greatly appreciated.
thanks again!
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-03-28 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 4:29 screening patch here before sending to devs Daniel Watson
2023-03-28 7:03 ` Lukas Bulwahn
2023-03-28 7:47 ` Daniel Watson [this message]
2023-03-28 7:57 ` Greg KH
2023-03-29 3:03 ` Daniel Watson
2023-03-29 3:12 ` Daniel Watson
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=ZCKbjmrrPc8C+NyD@trent-reznor \
--to=ozzloy@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=lukas.bulwahn@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