mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Gerrit Huizenga <gh@us.ibm.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ckrm-tech@lists.sourceforge.net
Subject: Re: [PATCH] CKRM [1/8]  Base CKRM events, mods to existing kernel code
Date: Thu, 24 Feb 2005 09:32:54 -0800	[thread overview]
Message-ID: <20050224173254.GA10086@kroah.com> (raw)
In-Reply-To: <E1D4FNZ-0006vj-00@w-gerrit.beaverton.ibm.com>

On Thu, Feb 24, 2005 at 01:33:53AM -0800, Gerrit Huizenga wrote:
> Core CKRM Event Callbacks.

I could wait 3 months with my comments like you did with your reply, but
I think I'll be a bit more timely, as I hope that you will be next time.

> On exec, fork, exit, real/effective gid/uid, use CKRM to associate
> tasks with appropriate class.
> 
> Addressed review comments:
> 
> Sam Ravnborg:  Use Makefile syntax correctly
> Dave Hansen:  Use of ## is annoying
> Greg KH:  Remove Changelogs;
>         Use __KERNEL__ correctly (if at all);
>         Consolidate CONFIG_ sections in header files;
>         Fix extern int get_exe_path_name().
>         Remove unused DEBUG code 
>         Convert enum to typedef in prep for sparce __bitwise use
> 
> Not yet Addressed:
> 
> Greg KH:
>         Use of __bitwise and sparse in enum's
>         Use of kernel list type

You forgot:
	Fix coding style
	Fix mix of whitespace (tabs and spaces)

Which you said you fixed up, but according to the code, you didn't :(

Also please add:
	Use kref instead of atomic counters
	Address Greg's comments about the fs.

I'll wait for these things to all get fixed up before reviewing the code
again.

thanks,

greg k-h

      parent reply	other threads:[~2005-02-24 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24  9:33 Gerrit Huizenga
2005-02-24 12:27 ` Alexey Dobriyan
2005-02-24 17:32 ` Greg KH [this message]

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=20050224173254.GA10086@kroah.com \
    --to=greg@kroah.com \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=gh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®