All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Sunitha Harish <sunithaharish04@gmail.com>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: raviteja28031990@gmail.com, Ratan Gupta <ratankgupta31@gmail.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Ed Tanous <ed@tanous.net>,
	gmills@linux.vnet.ibm.com, abhilash.kollam@gmail.com
Subject: Re: D-bus model proposal for pay for access features - LicenseService at OpenBMC
Date: Fri, 20 Oct 2023 15:36:26 +1030	[thread overview]
Message-ID: <7be0e5989986a85748ba2af7e1ee0014a20d658b.camel@codeconstruct.com.au> (raw)
In-Reply-To: <3fbaa94e-391d-4d3a-95fb-259503e94dd3@gmail.com>

On Thu, 2023-10-19 at 15:56 +0530, Sunitha Harish wrote:
> 
> More over this new meta-oe work will turn out to be costly.

It's a bit of a tangent, but I have to ask: What's the basis for the
assertion that adding a recipe to meta-openembedded or some other
upstream layer will be costly? That's not at all my experience or
expectation.

Andrew

  parent reply	other threads:[~2023-10-20  5:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 18:15 D-bus model proposal for pay for access features Ratan Gupta
2021-05-04  7:41 ` Ratan Gupta
2021-05-04 14:21   ` Mike Jones
2021-05-04 17:02 ` Ed Tanous
2021-05-04 21:18   ` Mike Jones
2021-05-05  0:00     ` Brad Bishop
2021-05-05  1:16     ` Ed Tanous
2021-05-04 23:38   ` Brad Bishop
2021-05-05 17:36     ` Patrick Williams
2023-10-06  4:51       ` D-bus model proposal for pay for access features - LicenseService at OpenBMC Sunitha Harish
2023-10-06 12:29         ` Patrick Williams
2023-10-06 17:17           ` Brad Bishop
2023-10-06 19:38             ` Patrick Williams
2023-10-13  2:02             ` Andrew Jeffery
2023-10-13  4:13               ` Brad Bishop
2023-10-13  6:02                 ` Sunitha Harish
2023-10-13  6:34                 ` Andrew Jeffery
2023-10-13 16:03                   ` Brad Bishop
2023-10-18  7:21                     ` Sunitha Harish
2023-10-18 13:18                       ` Brad Bishop
2023-10-19 10:26                         ` Sunitha Harish
2023-10-19 10:48                           ` Sunitha Harish
2023-10-20  5:06                           ` Andrew Jeffery [this message]
2023-10-20  5:42                             ` Sunitha Harish
2023-10-20  5:57                               ` Abhilash Kollam
2023-10-06 17:55           ` Patrick Williams

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=7be0e5989986a85748ba2af7e1ee0014a20d658b.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=abhilash.kollam@gmail.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=ed@tanous.net \
    --cc=gmills@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ratankgupta31@gmail.com \
    --cc=raviteja28031990@gmail.com \
    --cc=sunithaharish04@gmail.com \
    /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.