From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: david.vrabel@citrix.com, peterhuewe@gmx.de,
"tpmdd-devel@lists.sourceforge.net"
<tpmdd-devel@lists.sourceforge.net>,
xen-devel@lists.xenproject.org, jgunthorpe@obsidianresearch.com,
boris.ostrovsky@oracle.com, tpmdd@selhorst.net,
Juergen Gross <JGross@suse.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] xen-tpmfront: correct return value check on xenbus_scanf()
Date: Thu, 7 Jul 2016 15:21:35 +0300 [thread overview]
Message-ID: <20160707122135.GA17711@intel.com> (raw)
In-Reply-To: <577E607902000078000FC2FA@prv-mh.provo.novell.com>
On Thu, Jul 07, 2016 at 06:00:25AM -0600, Jan Beulich wrote:
> >>> On 07.07.16 at 12:38, <jarkko.sakkinen@linux.intel.com> wrote:
> > On Thu, Jul 07, 2016 at 01:35:54PM +0300, Jarkko Sakkinen wrote:
> >> On Thu, Jul 07, 2016 at 02:04:00AM -0600, Jan Beulich wrote:
> >> > Only a positive return value indicates success.
> >> >
> >> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >>
> >> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> >
> > Applied. Should this be CC'd to stable or not?
>
> Actually the Xen code maintainers dislike this kind of change
> (expressed in reply to a change elsewhere in the tree), so
> maybe you want to sync with them whether to pull it back out.
> In any event I don't think it needs Cc-ing to stable@.
OK, it's in my master branch (bleeding edge) so no harm done yet.
> Jan
/Jarkko
next prev parent reply other threads:[~2016-07-07 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 8:04 [PATCH] xen-tpmfront: correct return value check on xenbus_scanf() Jan Beulich
2016-07-07 10:35 ` Jarkko Sakkinen
[not found] ` <577E291002000078000FBF18-rw/UEucdPrvD8XXLLHKrIiOjQekVJEpY@public.gmane.org>
2016-07-07 10:35 ` Jarkko Sakkinen
2016-07-07 10:38 ` Jarkko Sakkinen
2016-07-07 12:00 ` Jan Beulich
[not found] ` <20160707103859.GA13815-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-07-07 12:00 ` Jan Beulich
2016-07-07 12:00 ` Jan Beulich
2016-07-07 12:21 ` Jarkko Sakkinen
2016-07-07 12:21 ` Jarkko Sakkinen [this message]
2016-07-07 10:38 ` Jarkko Sakkinen
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=20160707122135.GA17711@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=peterhuewe@gmx.de \
--cc=stable@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
--cc=xen-devel@lists.xenproject.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.