From: Kees Cook <keescook@chromium.org>
To: Allen Pais <allen.lkml@gmail.com>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] linux/kernel.h: add container_from()
Date: Wed, 26 Aug 2020 19:31:40 -0700 [thread overview]
Message-ID: <202008261929.A50D0DB3E8@keescook> (raw)
In-Reply-To: <20200827013636.149307-1-allen.lkml@gmail.com>
On Thu, Aug 27, 2020 at 07:06:36AM +0530, Allen Pais wrote:
> Introduce container_from() as a generic helper instead of
> sub-systems defining a private from_* API
> (Eg: from_tasklets recently introduced in
> 12cc923f1ccc: Tasklet: Introduce new initialization API)
>
> The helper is similar to container_of() in argument order
> with the difference of naming the containing structure instead
> of having to specify its type.
>
> Suggested-by: James E.J. Bottomley <James.Bottomley@HansenPartnership.com>
> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Suggested-by: Jens Axboe <axboe@kernel.dk>
> Signed-off-by: Allen Pais <allen.lkml@gmail.com>
Acked-by: Kees Cook <keescook@chromium.org>
Who can carry this so it can get used by multiple trees? Should I keep a
git branch folks should merge when taking Allen's conversion patches?
(In the future we can do a treewide replacement of the
subsystem-specific from*() macros into container_from())
Thanks!
--
Kees Cook
next prev parent reply other threads:[~2020-08-27 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 1:36 [PATCH] linux/kernel.h: add container_from() Allen Pais
2020-08-27 2:31 ` Kees Cook [this message]
2020-08-27 12:19 ` Greg Kroah-Hartman
2020-08-27 17:50 ` Kees Cook
2020-08-27 18:04 ` Linus Torvalds
2020-08-27 18:32 ` James Bottomley
2020-08-27 18:40 ` Linus Torvalds
2020-08-27 18:48 ` Linus Torvalds
2020-08-27 19:28 ` Kees Cook
2020-08-27 20:46 ` Linus Torvalds
2020-08-27 21:36 ` Al Viro
2020-08-27 22:14 ` Kees Cook
2020-08-28 7:09 ` Allen
2020-08-28 7:07 ` Allen
2020-08-27 18:07 ` Rasmus Villemoes
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=202008261929.A50D0DB3E8@keescook \
--to=keescook@chromium.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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