From: Patrick Williams <patrick@stwcx.xyz>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: "Patton, Schuyler" <spatton@ti.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [EXTERNAL] Re: new port seeing ipmid exiting with seg fault
Date: Fri, 23 Sep 2022 16:48:35 -0500 [thread overview]
Message-ID: <Yy4ps2Zhvaj8km2w@heinlein> (raw)
In-Reply-To: <675085d8-46d0-4eac-b6e5-40c9ad868dc4@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
Hello Schuyler,
On Fri, Sep 23, 2022 at 09:36:30AM +0930, Andrew Jeffery wrote:
> On Thu, 22 Sep 2022, at 15:14, Patton, Schuyler wrote:
> > Apologies as I am new to OpenBMC but I was looking for guidance on
> > which ipmid commit I should use beyond the bfd3a17 commit that seg
> > faults.
> >
>
> You'll need to reproduce the issue against the upstream code before we
> can help much further here.
To reiterate, this is really the answer for all repositories. We don't
have people that support release branches of code. Most people work off
HEAD in this project.
If you find a bug either the latest commit of a repository or the version
pointed to by the recipe in the latest commit of openbmc/openbmc, someone
is much more likely to look into it. If you are trying to report bugs on
something older it is quite likely going to get very little response.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-23 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 15:15 new port seeing ipmid exiting with seg fault Patton, Schuyler
2022-08-30 1:59 ` Andrew Jeffery
2022-09-22 5:44 ` [EXTERNAL] " Patton, Schuyler
2022-09-23 0:06 ` Andrew Jeffery
2022-09-23 21:48 ` Patrick Williams [this message]
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=Yy4ps2Zhvaj8km2w@heinlein \
--to=patrick@stwcx.xyz \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=spatton@ti.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 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 NNTP newsgroup(s).