openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Geissler <geissonator@gmail.com>
To: Thang Nguyen <thang@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Request to create ampere-platform-mgmt and ampere-ipmi-oem repos
Date: Mon, 7 Jun 2021 07:59:54 -0500	[thread overview]
Message-ID: <8EB56E60-53B3-4671-A64E-9F2FA73EB77E@gmail.com> (raw)
In-Reply-To: <1afee506-f30e-9f2e-9614-566e58ca25c5@os.amperecomputing.com>



> On Jun 7, 2021, at 3:45 AM, Thang Nguyen <thang@os.amperecomputing.com> wrote:
> 
> 
> On 03/05/2021 21:33, Brad Bishop wrote:
>> On Fri, Apr 16, 2021 at 09:05:36AM +0700, Thang Nguyen wrote:
>>> Hi Brad,
>>> 
>>> Can you help create 2 new repositories for Ampere specific codes:
>>> 
>>> - ampere-platform-mgmt: contains codes for Ampere specific applications to monitor and control Ampere's Host like RAS error handling, Temp event, ...
>>> 
>>> - ampere-ipmi-oem: contains codes for Ampere specific IPMI command support.
>> 
>> ampere-ipmi-oem is ready for your use.
>> 
>> thx - brad
> 
> Hi Brad,
> 
> Can you help enable CI for the ampere-ipmi-oem repo? It does not trigger CI when adding new patch in gerrit.

Done

> 
> 
> Thx - ThangQ
> 


      reply	other threads:[~2021-06-07 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  2:05 Request to create ampere-platform-mgmt and ampere-ipmi-oem repos Thang Nguyen
2021-04-23 13:31 ` Patrick Williams
2021-04-24 12:48   ` Thang Nguyen
2021-04-30 14:25     ` Patrick Williams
2021-05-04  1:47       ` Thang Nguyen
2021-05-11  9:00         ` Thang Nguyen
2021-05-03 14:33 ` Brad Bishop
2021-05-04  1:45   ` Thang Nguyen
2021-06-07  8:45   ` Thang Nguyen
2021-06-07 12:59     ` Andrew Geissler [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=8EB56E60-53B3-4671-A64E-9F2FA73EB77E@gmail.com \
    --to=geissonator@gmail.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=thang@os.amperecomputing.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).