public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Borislav Petkov <bp@alien8.de>, LKML <linux-kernel@vger.kernel.org>
Cc: Borislav Petkov <bp@suse.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] param, charp: Cache val length
Date: Mon, 18 Feb 2013 21:54:22 +1030	[thread overview]
Message-ID: <87txp9j255.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1361178750-17915-1-git-send-email-bp@alien8.de>

Borislav Petkov <bp@alien8.de> writes:
> From: Borislav Petkov <bp@suse.de>
>
> ... instead of doing strlen twice.

I'm delighted with your enthusiasm for making trivial changes, but I
have trouble sharing in it.

In this case, it's so marginal that I'll leave the status quo.

Thanks,
Rusty.

  reply	other threads:[~2013-02-19  8:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18  9:12 [PATCH] param, charp: Cache val length Borislav Petkov
2013-02-18 11:24 ` Rusty Russell [this message]
2013-02-19 11:59   ` Borislav Petkov

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=87txp9j255.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --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