All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Dan McGregor <danismostlikely@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nfs-utils: bugfix: adjust name of statd service unit
Date: Wed, 23 Mar 2016 09:47:39 +0100	[thread overview]
Message-ID: <1458722860-17353-1-git-send-email-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <CACS+7ZTw_vCMo5dfGCT9PyUMFvq7QaoXRbK5Ou60Y=m=YGhL_g@mail.gmail.com>

Hi Dan,

On Tue, Mar 22, 2016 at 06:34:08PM -0600, Dan McGregor wrote:
> On 17 Feb 2016 3:48 a.m., "Ulrich Ölmann" <u.oelmann@pengutronix.de> wrote:
> >
> > Upstream nfs-utils use 'rpc-statd.service' and Yocto introduced
> > 'nfs-statd.service' instead but forgot to update the mount.nfs helper
> > 'start-statd' accordingly.
> >
> > Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
> > ---
> >  .../files/bugfix-adjust-statd-service-name.patch   | 34
> ++++++++++++++++++++++
> >  .../nfs-utils/nfs-utils_1.3.3.bb                   |  1 +
> >  2 files changed, 35 insertions(+)
> >  create mode 100644
> meta/recipes-connectivity/nfs-utils/files/bugfix-adjust-statd-service-name.patch

[...]

> I just got bit by this in jethro. Can it be backported?

Backporting should be fairly simple, I assume you didn't give it a go.
Try the patch that comes in my reply to this mail. It is untested as I don't
have the time at the moment, hence please report back if it works.

Regards
Ulrich


  reply	other threads:[~2016-03-23  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  9:30 [PATCH] nfs-utils: bugfix: adjust name of statd service unit Ulrich Ölmann
2016-03-23  0:34 ` Dan McGregor
2016-03-23  8:47   ` Ulrich Ölmann [this message]
2016-03-23  8:47     ` [jethro][PATCH] " Ulrich Ölmann
2016-03-23 13:18     ` [PATCH] " Dan McGregor
2016-03-23 13:38       ` Ulrich Ölmann
2016-03-24 21:48 ` Burton, Ross
2016-03-24 22:11   ` Dan McGregor

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=1458722860-17353-1-git-send-email-u.oelmann@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=danismostlikely@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.