From: Sean Anderson <sean.anderson@seco.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
meta-freescale@lists.yoctoproject.org,
Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Ting Liu <ting.liu@nxp.com>, Jun Zhu <junzhu@nxp.com>,
Ahmed Mansour <ahmed.mansour@nxp.com>,
Zhenhua Luo <zhenhua.luo@nxp.com>,
Priyanka Jain <priyanka.jain@nxp.com>,
Rajesh Bhagat <rajesh.bhagat@nxp.com>,
Pramod Kumar <pramod.kumar_1@nxp.com>,
Alison Wang <alison.wang@nxp.com>,
Mingkai Hu <Mingkai.Hu@nxp.com>,
Udit Agarwal <udit.agarwal@nxp.com>,
Otavio Salvador <otavio.salvador@ossystems.com.br>,
Chunrong Guo <chunrong.guo@nxp.com>
Subject: Submitting patches for QorIQ components
Date: Fri, 4 Mar 2022 14:36:19 -0500 [thread overview]
Message-ID: <048d37a0-d7f6-fe72-e4b8-86072daa223b@seco.com> (raw)
Hi all,
Where should patches for QorIQ components [1] go? I have some patches
for meta-qoriq [2] and dce [3], but I can't figure out where to send
them to. There is no mailing list in the READMEs, and there is no way to
send pull requests like on the former github repos [4]. I tried emailing
the most recent committers directly, but got no response.
--Sean
[1] https://source.codeaurora.org/external/qoriq/qoriq-components/
[2] https://source.codeaurora.org/external/qoriq/qoriq-components/meta-qoriq/
[3] https://source.codeaurora.org/external/qoriq/qoriq-components/dce/
[4] https://github.com/qoriq-open-source/meta-qoriq-demos
reply other threads:[~2022-03-04 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=048d37a0-d7f6-fe72-e4b8-86072daa223b@seco.com \
--to=sean.anderson@seco.com \
--cc=Mingkai.Hu@nxp.com \
--cc=ahmed.mansour@nxp.com \
--cc=alison.wang@nxp.com \
--cc=chunrong.guo@nxp.com \
--cc=junzhu@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=pramod.kumar_1@nxp.com \
--cc=priyanka.jain@nxp.com \
--cc=rajesh.bhagat@nxp.com \
--cc=shawnguo@kernel.org \
--cc=ting.liu@nxp.com \
--cc=u-boot@lists.denx.de \
--cc=udit.agarwal@nxp.com \
--cc=zhenhua.luo@nxp.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 read-only IMAP folder(s) and NNTP newsgroup(s).