All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH V2] Check return code for IBM Olympic /proc entry
Date: Thu, 26 May 2005 06:34:37 +0000	[thread overview]
Message-ID: <20050526063437.GJ3851@nd47.coderock.org> (raw)
In-Reply-To: <1116404511.1169.15.camel@itchy.kirkandsheila.com>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

On 25/05/05 23:22 -0700, Kirk True wrote:
> Hi Domen,
> 
> On Wed, 2005-05-25 at 15:07 +0200, Domen Puncer wrote:
> > On 18/05/05 01:21 -0700, Kirk True wrote:
> > > The IBM Olympic driver assumes that the call to create_proc_read_entry 
> > > always succeeds. This patch simply logs appropriately whether in 
> > > actuality it was created or not.
> > > 
> > > This falls under the 'Audit return codes (and handle failure correctly) 
> > > for create_proc_*()' item on the TODO list. Also added KERN_* constants
> > > as per Christophe Lucas' recommendation.
> > > 
> > >         Signed-off-by: Kirk True <kirk@kirkandsheila.com>
> >   ^^ please don't
> 
> Sorry to be daft, but "please don't" do what exactly? I tried to follow
> the guidelines. My apologies in advance for the error.

Put spaces before "Signed-off-by" :-)
Now that check SubmittingPatches, I see it's there too.
Still, most of patches don't do it, and I imagine it can break scripts.

> > > -		create_proc_read_entry(proc_name,0,NULL,olympic_proc_info,(void *)dev) ; 
> > > -		printk("Olympic: Network Monitor information: /proc/%s\n",proc_name); 
> > > +		proc_dir_entry = create_proc_read_entry(proc_name,0,NULL,olympic_proc_info,(void *)dev) ; 
> > 
> > I removed the unneeded (void*) cast (couldn't resist) and trailing
> > whitespace here.
> 
> I didn't do too much beyond the specific request to handle the audit
> code. I'm coming from the 'try to change it as little as possible
> because you don't know what you're doing just yet' mindset :)

Well... stripping trailing whitespace is not too much to ask.
Anyway, patch should be in next -kj. Thanks.


	Domen

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-05-26  6:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  8:21 [KJ] [PATCH V2] Check return code for IBM Olympic /proc entry Kirk True
2005-05-25 13:07 ` Domen Puncer
2005-05-26  6:22 ` Kirk True
2005-05-26  6:34 ` Domen Puncer [this message]
2005-05-26  6:49 ` Kirk True

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=20050526063437.GJ3851@nd47.coderock.org \
    --to=domen@coderock.org \
    --cc=kernel-janitors@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 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.