mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Haavard Skinnemoen <hskinnemoen@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/3] AVR32: Fine-tuning for two function implementations
Date: Wed, 18 Jan 2017 16:12:17 +0100	[thread overview]
Message-ID: <20170118151217.GA26808@samfundet.no> (raw)
In-Reply-To: <308dc151-c874-dfe7-64f9-24a63fc66883@users.sourceforge.net>

Around Wed 18 Jan 2017 14:45:07 +0100 or thereabout, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Wed, 18 Jan 2017 14:40:04 +0100
> 
> A few update suggestions were taken into account
> from static source code analysis.
> 
> Markus Elfring (3):
>   Return directly after a failed access_ok() in setup_rt_frame()
>   Delete an unnecessary variable initialisation in setup_rt_frame()
>   Return an error code only as a constant in sys_cacheflush()
> 
>  arch/avr32/kernel/signal.c |  5 ++---
>  arch/avr32/mm/cache.c      | 21 +++++----------------
>  2 files changed, 7 insertions(+), 19 deletions(-)

Ack, I guess it slightly simplifies reading. Will add to linux-avr32 git
tree.

-- 
mvh
Hans-Christian Noren Egtvedt

      parent reply	other threads:[~2017-01-18 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 13:45 SF Markus Elfring
2017-01-18 13:46 ` [PATCH 1/3] AVR32: Return directly after a failed access_ok() in setup_rt_frame() SF Markus Elfring
2017-01-18 13:48 ` [PATCH 2/3] AVR32: Delete an unnecessary variable initialisation " SF Markus Elfring
2017-01-18 13:50 ` [PATCH 3/3] AVR32: Return an error code only as a constant in sys_cacheflush() SF Markus Elfring
2017-01-18 15:12 ` Hans-Christian Noren Egtvedt [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=20170118151217.GA26808@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=elfring@users.sourceforge.net \
    --cc=hskinnemoen@gmail.com \
    --cc=kernel-janitors@vger.kernel.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

Powered by JetHome