All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>, Don Slutz <dslutz@verizon.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2 1/5] Add Emacs local variables to source files.
Date: Wed, 8 Jan 2014 01:27:54 +0000	[thread overview]
Message-ID: <52CCA99A.3080709@citrix.com> (raw)
In-Reply-To: <20140107171602.1f9d8153@mantra.us.oracle.com>

On 08/01/2014 01:16, Mukesh Rathor wrote:
> On Tue,  7 Jan 2014 19:25:44 -0500
> Don Slutz <dslutz@verizon.com> wrote:
>
>> These 2 files are changed in this patch set.  So add the allowed
>> "Emacs local variables" from CODING_STYLE.
>>
>> Signed-off-by: Don Slutz <dslutz@verizon.com>
> Will let some emacs user ack these... "vim" rules!!
>
> Mukesh

Wasn't there a patch a little while back to add equivalent vim rules to
each of the files (or at least a thread suggesting a patch)?  In the
interest of cooperation, it is only fair.

As a fellow emacsian,

Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

As for 4.4-ness:  If the rest of the series is deemed ok for a
release-ack, then this should go in for completeness.  If part of the
series is decided to be deferred, then this warrants deferring as well.

~Andrew

  reply	other threads:[~2014-01-08  1:27 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  0:25 [BUGFIX][PATCH v2 0/5] gdbsx: fix 3 bugs Don Slutz
2014-01-08  0:25 ` [PATCH v2 1/5] Add Emacs local variables to source files Don Slutz
2014-01-08  1:16   ` Mukesh Rathor
2014-01-08  1:27     ` Andrew Cooper [this message]
2014-01-08  9:51       ` Ian Campbell
2014-01-08 15:58         ` Ian Campbell
2014-01-08  0:25 ` [BUGFIX][PATCH v2 2/5] dbg_rw_guest_mem: need to call put_gfn in error path Don Slutz
2014-01-08  0:55   ` Andrew Cooper
2014-01-08  1:06     ` Don Slutz
2014-01-08  1:15       ` Andrew Cooper
2014-01-08  1:14     ` Mukesh Rathor
2014-01-08  1:44     ` Mukesh Rathor
2014-01-08  2:30       ` Andrew Cooper
2014-01-08  2:44         ` Mukesh Rathor
2014-01-08 10:40     ` Ian Campbell
2014-01-08 14:01       ` Don Slutz
2014-01-08  8:36   ` Jan Beulich
2014-01-08 13:48     ` Don Slutz
2014-01-08  0:25 ` [PATCH v2 3/5] dbg_rw_guest_mem: Conditionally enable debug log output Don Slutz
2014-01-08  1:38   ` Mukesh Rathor
2014-01-08 10:38   ` Ian Campbell
2014-01-08 14:28     ` Don Slutz
2014-01-08 16:47       ` Ian Campbell
2014-01-08 17:04         ` Tim Deegan
2014-01-08 17:44           ` Ian Campbell
2014-01-08 18:10             ` Tim Deegan
2014-01-09  8:41               ` Ian Campbell
2014-01-09 10:32                 ` Tim Deegan
2014-01-09  0:38             ` Mukesh Rathor
2014-01-09  9:59               ` Ian Campbell
2014-01-09 16:08                 ` Don Slutz
2014-01-09 16:30                   ` Jan Beulich
2014-01-09 17:56                     ` Don Slutz
2014-01-10 17:13                       ` Ian Campbell
2014-01-10 21:15                         ` Don Slutz
2014-01-10 22:08                           ` [PATCH v3 " Don Slutz
2014-01-10  1:54                 ` [PATCH v2 " Mukesh Rathor
2014-01-08  0:25 ` [BUGFIX][PATCH v2 4/5] xg_read_mem: Report on error Don Slutz
2014-01-08  1:16   ` Mukesh Rathor
2014-01-08  0:25 ` [BUGFIX][PATCH v2 5/5] xg_main: If XEN_DOMCTL_gdbsx_guestmemio fails then force error Don Slutz
2014-01-08  1:11   ` Mukesh Rathor
2014-01-08 10:35   ` Ian Campbell
2014-01-08 14:39     ` Don Slutz
2014-01-08  8:28 ` [BUGFIX][PATCH v2 0/5] gdbsx: fix 3 bugs Jan Beulich
2014-01-08 14:43   ` Don Slutz

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=52CCA99A.3080709@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=mukesh.rathor@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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.