From: Christoph Hellwig <hch@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Converting struct timer_list callback argument to struct timer_list *
Date: Fri, 1 Sep 2017 03:44:56 -0700 [thread overview]
Message-ID: <20170901104456.GA25892@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1709011219590.1857@nanos>
On Fri, Sep 01, 2017 at 12:21:46PM +0200, Thomas Gleixner wrote:
> On Fri, 1 Sep 2017, Christoph Hellwig wrote:
>
> > Good work!
> >
> > I just think that the TIMER_CONTAINER name is revolting.
> >
> > The usual name for such a helper fitting other uses like lists
> > and rbtrees would be timer_entry, and that also reads much better.
>
> I think the plan is to remove that thing afterward, because then the
> callback function is:
>
> void func(struct timer_list *timer)
>
> So I don't mind the ugly name as it should be simply removed once the tree
> is converted over.
Well, we can't just remove it, we could just replace it with
container_of(). lists and rbtrees just keep their list_entry and
rb_entry wrappers for timer_of, so we could save us the additional
churn by naming it timer_entry and just keeping it.
next prev parent reply other threads:[~2017-09-01 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 23:39 Converting struct timer_list callback argument to struct timer_list * Kees Cook
2017-08-31 20:13 ` Thomas Gleixner
2017-08-31 23:32 ` Kees Cook
2017-09-01 10:08 ` Christoph Hellwig
2017-09-01 10:21 ` Thomas Gleixner
2017-09-01 10:44 ` Christoph Hellwig [this message]
2017-09-01 16:24 ` Kees Cook
2017-09-03 7:37 ` Christoph Hellwig
2017-09-03 20:18 ` Kees Cook
2017-09-04 6:07 ` Christoph Hellwig
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=20170901104456.GA25892@infradead.org \
--to=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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