From: Kees Cook <keescook@chromium.org>
To: Allen <allen.lkml@gmail.com>
Cc: Oscar Carter <oscar.carter@gmx.com>,
Kernel Hardening <kernel-hardening@lists.openwall.com>
Subject: Re: Clarification about the series to modernize the tasklet api
Date: Tue, 14 Jul 2020 16:20:49 -0700 [thread overview]
Message-ID: <202007141617.DB13889164@keescook> (raw)
In-Reply-To: <CAOMdWSLFXhS=KY9fG4SH5Oe9oEgj4sGmrRN8MOe9NZzJtdJOww@mail.gmail.com>
On Tue, Jul 14, 2020 at 07:57:06PM +0530, Allen wrote:
> >
> > My bad, I should have told you that github was just a placeholder for
> > WIP patches. I have been testing a set of patches regularly, no issues.
> > I shall push the updated branch.
> >
>
> Made some progress today. I have a few more things to complete
> before the series can go out for review. I have pushed out the changes to:
>
> https://github.com/allenpais/tasklets/commits/tasklets_V1
Nice! One style nit is the Subject lines needs spaces after the ":"s.
For example, "crypto:hifn_795x: replace tasklet...." should be
"crypto: hifn_795x: replace tasklet...."
I did this to fix it:
rm 0*.patch
git format-patch 7f51b77d527325bfa1dd5da21810765066bd60ff
git reset --hard 7f51b77d527325bfa1dd5da21810765066bd60ff
perl -pi.old -e \
's/Subject: \[PATCH([^\]]+)\] ([^:]+):([^ ])/Subject: [PATCH\1] \2: \3/' 0*patch
git am 0*.patch
--
Kees Cook
next prev parent reply other threads:[~2020-07-14 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 17:42 Clarification about the series to modernize the tasklet api Oscar Carter
2020-07-13 9:25 ` Allen
2020-07-13 10:24 ` Allen
2020-07-13 16:27 ` Kees Cook
2020-07-14 5:09 ` Allen
2020-07-18 12:34 ` Oscar Carter
2020-07-14 0:02 ` Kees Cook
2020-07-14 5:12 ` Allen
2020-07-14 14:27 ` Allen
2020-07-14 23:20 ` Kees Cook [this message]
2020-07-15 7:34 ` Allen
2020-07-15 14:51 ` Allen
2020-07-15 15:14 ` Kees Cook
2020-07-15 15:21 ` Allen
2020-07-15 15:29 ` Kees Cook
2020-07-15 15:33 ` Allen
2020-07-13 16:16 ` Kees Cook
2020-07-18 12:21 ` Oscar Carter
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=202007141617.DB13889164@keescook \
--to=keescook@chromium.org \
--cc=allen.lkml@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=oscar.carter@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.