From: Jeff Law <jeffreyalaw@gmail.com>
To: "Shinde, Yash" <Yash.Shinde@windriver.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "MacLeod, Randy" <Randy.MacLeod@windriver.com>,
"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: Re: GCC Patch Tracking [https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html]
Date: Tue, 27 Dec 2022 10:39:51 -0700 [thread overview]
Message-ID: <b92b0189-9729-ae38-2729-38e19dc5879c@gmail.com> (raw)
In-Reply-To: <SJ1PR11MB61295BE5AD8D3F476AF3A538EBEB9@SJ1PR11MB6129.namprd11.prod.outlook.com>
On 12/21/22 10:36, Shinde, Yash wrote:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html
> Submission Date- Wed, 17 Aug 2022
> Upstream-Status: Submitted
>
> The given GCC patch is with it’s current status as ‘Submitted’ but still is not taken to the upstream. Please let us know about why the patch is not taken to the upstream or let us know if there is any problem in including it in upstream.
The powerpc maintainers will need to review the patch and decide if they
want to take it now, take it later or reject.
jeff
prev parent reply other threads:[~2022-12-27 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 17:36 Shinde, Yash
2022-12-27 17:39 ` Jeff Law [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=b92b0189-9729-ae38-2729-38e19dc5879c@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Yash.Shinde@windriver.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.purdie@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).