All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Laplante" <chris.laplante@agilent.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [hardknott][PATCH] bitbake: server: Fix early parsing errors preventing zombie bitbake
Date: Wed, 8 Sep 2021 17:27:22 +0000	[thread overview]
Message-ID: <DM8PR12MB543089FBA26942E145A386568BD49@DM8PR12MB5430.namprd12.prod.outlook.com> (raw)
In-Reply-To: <16A0207AC2905018.25648@lists.openembedded.org>

Hello,

> If the client process never sends cooker data, the server timeout will be 0.0,
> not None. This will prevent the server from exiting, as it is waiting for a new
> client. In particular, the client will disconnect with a bad "INHERIT" line, such
> as:
> 
>     INHERIT += "this-class-does-not-exist"
> 
> Instead of checking explicitly for None, check for a false value, which means
> either 0.0 or None.
> 
> (Bitbake rev: 7668057f8565655611de23d143432d1c05dae3ce)
> 
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> (cherry picked from commit 881005ec405f26b8f7f4b41505d69579e83b69c4)

Was this the correct for me to request application of this patch to hardknott branch? I've never tried to submit a patch to something other than master.

No rush obviously, just wanted to check that I was doing it right.

Thanks,
Chris 

       reply	other threads:[~2021-09-08 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16A0207AC2905018.25648@lists.openembedded.org>
2021-09-08 17:27 ` Chris Laplante [this message]
2021-09-09  1:16   ` [OE-core] [hardknott][PATCH] bitbake: server: Fix early parsing errors preventing zombie bitbake Anuj Mittal
2021-09-13 14:28     ` Chris Laplante

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=DM8PR12MB543089FBA26942E145A386568BD49@DM8PR12MB5430.namprd12.prod.outlook.com \
    --to=chris.laplante@agilent.com \
    --cc=JPEWhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.