All of lore.kernel.org
 help / color / mirror / Atom feed
From: rwxybh <rwxybh@126.com>
To: Ian Campbell <Ian.Campbell@citrix.com>, Wei Liu <liuw@liuw.name>
Cc: "rwxybh@123.com" <rwxybh@123.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Fix function libxl__domain_resume_device_model
Date: Tue, 30 Jul 2013 20:39:38 +0800	[thread overview]
Message-ID: <2013073020393614338768@126.com> (raw)
In-Reply-To: 1375187323.11701.106.camel@kazak.uk.xensource.com


[-- Attachment #1.1: Type: text/plain, Size: 2040 bytes --]

Of course, Ian.

From: Ian Campbell
Date: 2013-07-30 20:28
To: Wei Liu
CC: rwxybh; rwxybh@123.com; xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [PATCH] Fix function libxl__domain_resume_device_model
On Tue, 2013-07-30 at 20:00 +0800, Wei Liu wrote:
> On Tue, Jul 30, 2013 at 8:37 AM, rwxybh <rwxybh@126.com> wrote:
> > Add a break point in function libxl__domain_resume_device_model
> >
> > Signed-off-by: rwxybh <rwxybh@126.com>
> 
> Is it OK to use alias rather than real name in SoB? I remember seeing that
> author should use real name in SoB but I'm not sure. Ignore this if I'm wrong.

I know the Linux guys have been picky about this in the past, although
I'm not sure they are 100% consistent (the one I'm thinking of had other
surrounding controversy).

In any case since rwxybh has previously posted with their real name I
think it would be OK to ask for an S-o-b containing it and sidestep
having to think about the issue? Bingheng, are you OK with me using the
following S-o-b instead of the one above?

> Signed-off-by: Bingheng Yan <rwxybh@126.com>

Ian.

> 
> 
> Wei.
> 
> > ---
> >  tools/libxl/libxl_dom.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
> > index b38d0a7..3eaf3ae 100644
> > --- a/tools/libxl/libxl_dom.c
> > +++ b/tools/libxl/libxl_dom.c
> > @@ -985,6 +985,7 @@ int libxl__domain_resume_device_model(libxl__gc *gc, uint32_t domid)
> >      case LIBXL_DEVICE_MODEL_VERSION_QEMU_XEN:
> >          if (libxl__qmp_resume(gc, domid))
> >              return ERROR_FAIL;
> > +       break;
> >      default:
> >          return ERROR_INVAL;
> >      }
> > --
> > 1.7.1
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

[-- Attachment #1.2: Type: text/html, Size: 4602 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-07-30 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  0:37 [PATCH] Fix function libxl__domain_resume_device_model rwxybh
2013-07-30  8:22 ` Roger Pau Monné
2013-07-30 12:00 ` Wei Liu
2013-07-30 12:28   ` Ian Campbell
2013-07-30 12:39     ` rwxybh [this message]
2013-07-30 13:04       ` Ian Campbell

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=2013073020393614338768@126.com \
    --to=rwxybh@126.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=liuw@liuw.name \
    --cc=rwxybh@123.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.