Openbmc archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: "Ambrozewicz, Adrian" <adrian.ambrozewicz@linux.intel.com>
Cc: cezary.zwolak@intel.com, openbmc@lists.ozlabs.org,
	liuxiwei@ieisystem.com, jozef.wludzik@intel.com
Subject: Re: openbmc/telemetry: First complaint of unresponsiveness
Date: Fri, 22 Dec 2023 15:40:43 -0600	[thread overview]
Message-ID: <ZYYCW2V-LDe6pQ9i@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <74ad915f-02b3-4c69-ab27-472bb9332388@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 611 bytes --]

On Thu, Dec 21, 2023 at 11:42:52AM +0100, Ambrozewicz, Adrian wrote:
> On 20.12.2023 17:56, Patrick Williams wrote:
> > On Wed, Dec 20, 2023 at 05:03:21PM +0100, Ambrozewicz, Adrian wrote:

> I would prefer to not dwell into further discussion here as certain 
> topics are far beyond my control. I'll just assure you we're trying to 
> do the best we can with resources available. Whenever similar related 
> issues or decisions to make arise in the future I will be surely better 
> equipped to make informed decisions aligned with general open source 
> consensus.

Ack.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-22 21:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 23:54 openbmc/telemetry: First complaint of unresponsiveness Andrew Jeffery
2023-12-20 14:18 ` Ambrozewicz, Adrian
2023-12-20 15:22   ` Patrick Williams
2023-12-20 16:03     ` Ambrozewicz, Adrian
2023-12-20 16:56       ` Patrick Williams
2023-12-20 22:58         ` Andrew Jeffery
2023-12-21  1:54           ` Patrick Williams
2023-12-21  9:12           ` Ambrozewicz, Adrian
2023-12-21 10:42         ` Ambrozewicz, Adrian
2023-12-22 21:40           ` Patrick Williams [this message]
2023-12-20 22:44   ` Andrew Jeffery

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=ZYYCW2V-LDe6pQ9i@heinlein.vulture-banana.ts.net \
    --to=patrick@stwcx.xyz \
    --cc=adrian.ambrozewicz@linux.intel.com \
    --cc=cezary.zwolak@intel.com \
    --cc=jozef.wludzik@intel.com \
    --cc=liuxiwei@ieisystem.com \
    --cc=openbmc@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).