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: Fri, 5 Nov 2021 00:18:20 -0400 [thread overview]
Message-ID: <CABoTLcRbdSk1WMDc4mfLHnZW1T0ccBUE-DNsRTonOzbtxKaXMg@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XfRJ--eXpZeC1TPbC+5cwVNQeSUjA8w-dvM-ABGpu3t7g@mail.gmail.com>
Hi Joel
> > I sent https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/48632
>
> I normally do this, but you're welcome to do it too. I'll merge your
> device tree update now, and if you could then update your bump to
> include that commit I'll +2 it.
Done. Thank you!
> I have a slightly horrible script that does the work for me.
I created the commit message manually this time. I hope I didn't get
the order backwards :-)
Oskar.
prev parent reply other threads:[~2021-11-05 4:19 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
2021-11-05 4:00 ` Joel Stanley
2021-11-05 4:18 ` Oskar Senft [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=CABoTLcRbdSk1WMDc4mfLHnZW1T0ccBUE-DNsRTonOzbtxKaXMg@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).