openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Oskar Senft <osk@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Joel Stanley <joel@jms.id.au>
Subject: Cherry-picking 5.16 commits into OpenBMC Linux?
Date: Wed, 3 Nov 2021 12:28:49 -0400	[thread overview]
Message-ID: <CABoTLcQHOcfvHkCGX0nMUxFzmTcceuBhL3CQERn66CT8UsSvwQ@mail.gmail.com> (raw)

Hi Joel

There are a few commit that I sent upstream that have been accepted by
the maintainers (i.e. have the appropriate "Reviewed-by" tags) that
are waiting for 5.16 to open.

I'm waiting for these patches to be available to be able to send a new
meta-tyan directory to OpenBMC for review.

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?

Specific patches:
https://lore.kernel.org/lkml/20211020164213.174597-1-osk@google.com/t/#m8f7ac85809049fadcabf6e0bed1ebab12e71f094
https://lore.kernel.org/linux-arm-kernel/20210909004920.1634322-1-osk@google.com/

There will also be an update to the DTS from the second patch once the
driver change from the first patch has fully landed. Or should I
better send that DTS change now and we'll take it into OpenBMC Linux
together?

Thanks
Oskar.

             reply	other threads:[~2021-11-03 16:29 UTC|newest]

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