All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Vlasenko <dvlasenk@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip:x86/asm] x86/asm/entry/32: Improve code readability
Date: Sun, 07 Jun 2015 20:26:58 +0200	[thread overview]
Message-ID: <55748CF2.9010101@redhat.com> (raw)
In-Reply-To: <tip-54ad726c51b7f7dffcc1dc379bedadee19f742f7@git.kernel.org>

On 06/07/2015 10:32 AM, tip-bot for Ingo Molnar wrote:
> Commit-ID:  54ad726c51b7f7dffcc1dc379bedadee19f742f7
> Gitweb:     http://git.kernel.org/tip/54ad726c51b7f7dffcc1dc379bedadee19f742f7
> Author:     Ingo Molnar <mingo@kernel.org>
> AuthorDate: Fri, 5 Jun 2015 13:02:28 +0200
> Committer:  Ingo Molnar <mingo@kernel.org>
> CommitDate: Fri, 5 Jun 2015 13:22:22 +0200
> 
> x86/asm/entry/32: Improve code readability
> 
> Make the 64-bit compat 32-bit syscall entry code a bit more readable:
> 
>  - eliminate whitespace noise
> 
>  - use consistent vertical spacing
> 
>  - use consistent assembly coding style similar to entry_64.S
> 
>  - fix various comments


Thank you!

           reply	other threads:[~2015-06-07 18:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <tip-54ad726c51b7f7dffcc1dc379bedadee19f742f7@git.kernel.org>]

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=55748CF2.9010101@redhat.com \
    --to=dvlasenk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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.