openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Oskar Senft <osk@google.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Cherry-picking 5.16 commits into OpenBMC Linux?
Date: Thu, 4 Nov 2021 23:52:22 -0400	[thread overview]
Message-ID: <CABoTLcRoC7aQ1e0V3FMbmRgvuMafib0qUHOuYZkORFOooGSYcQ@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XcRfTkZynhnmYn0ySq82MjJQZwgy_4UjKpcxYgF5cG7xw@mail.gmail.com>

Hi Joel

> > Would it be possible to cherry-pick these commits into the OpenBMC
> > Linux tree to speed up this process? Or is this something you
> > generally prefer to not do?
>
> Yes, this is exactly what the tree is for.
Aha, cool! I'm starting to get the picture :-)

> > https://lore.kernel.org/linux-arm-kernel/20210909004920.1634322-1-osk@google.com/
>
> If you take a look at the dev-5.15 branch, you can see that this one
> is already applied.
Awesome, thank you! I didn't even think of looking there. I thought
I'd have to wait for 5.16 to manifest itself.

I sent https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/48632 to
forward the commit for linux-aspeed. I hope that was right? Or does
someone (you?) do that periodically anyway? I did test (build and run)
and it works as expected.

Oskar.

  parent reply	other threads:[~2021-11-05  3:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 16:28 Cherry-picking 5.16 commits into OpenBMC Linux? Oskar Senft
2021-11-03 23:22 ` Joel Stanley
2021-11-04  7:25   ` Thang Nguyen
2021-11-05  3:52   ` Oskar Senft [this message]
2021-11-05  4:00     ` Joel Stanley
2021-11-05  4:18       ` Oskar Senft

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=CABoTLcRoC7aQ1e0V3FMbmRgvuMafib0qUHOuYZkORFOooGSYcQ@mail.gmail.com \
    --to=osk@google.com \
    --cc=joel@jms.id.au \
    --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 NNTP newsgroup(s).