From: Allen <allen.lkml@gmail.com>
To: Kees Cook <keescook@chromium.org>
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: Wed, 15 Jul 2020 20:21:12 +0530 [thread overview]
Message-ID: <CAOMdWSLZUpp+1DLr93vwD2P0-DHxSNFKFPDXB2nhq+x86JnLHw@mail.gmail.com> (raw)
In-Reply-To: <CAOMdWSKURaD=09LCmv1vSk8Js-uK1r5vVWYtPB_bEhDZJmFACw@mail.gmail.com>
> >
> > 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
>
> Thanks, I shall have it fixed.
Fixed all the patches and cleaned them up.
https://github.com/allenpais/tasklets/commits/tasklets_V2
Build tested with "make allmodconfig" and boot tested on x86, Raspberry Pi3,
qemu(arm64 and x86).
I will have the drivers in staging converted in a day or two.
I haven't yet added the patch to completely remove the old API, I
think it's best
for the current series to be accepted upstream and only when all of them have
been accepted it will be right to send the clean up patch.
Please take a look and let me know if they are good to go out for review.
--
- Allen
next prev parent reply other threads:[~2020-07-15 14:51 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
2020-07-15 7:34 ` Allen
2020-07-15 14:51 ` Allen [this message]
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=CAOMdWSLZUpp+1DLr93vwD2P0-DHxSNFKFPDXB2nhq+x86JnLHw@mail.gmail.com \
--to=allen.lkml@gmail.com \
--cc=keescook@chromium.org \
--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 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).