All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] credit1: Use atomic bit operations for the flags structure
Date: Mon, 4 Mar 2013 11:42:19 +0000	[thread overview]
Message-ID: <5134889B.4080700@eu.citrix.com> (raw)
In-Reply-To: <513496C902000078000C2C7A@nat28.tlf.novell.com>

On 04/03/13 11:42, Jan Beulich wrote:
>>>> On 04.03.13 at 12:06, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>> Ping?
> I could ack it, but wouldn't be permitted to commit without Keir's ack,
> so it's all left to him... Same for the two credit2 patches of yours (I
> reckon the resend today doesn't really have any changes over what
> you had sent last week).

Is that how it works?  I thought the main point was just that everything 
has to have a suitable ack, and not even committers can ack their own 
stuff; so my SoB + your ack should be sufficient. That seems to be how 
IanC and IanJ do stuff.

You are correct regarding the credit2 patches -- I resent them because 
the first batch I sent last week had a mistake, and I wasn't sure the 
second batch (with the fix) was distinguishable if someone got a bit 
confused.  So I thought it safest to send another copy explicitly with "v3".

  -George

  reply	other threads:[~2013-03-04 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 14:29 [PATCH] credit1: Use atomic bit operations for the flags structure George Dunlap
2013-03-04 11:06 ` George Dunlap
2013-03-04 11:42   ` Jan Beulich
2013-03-04 11:42     ` George Dunlap [this message]
2013-03-04 12:10       ` Jan Beulich

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=5134889B.4080700@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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.