Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Tom Hochstein <tom.hochstein@nxp.com>,
	Antoine Manache <a.manache@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] security_flags.inc: fix flags missing from SDK toolchain
Date: Wed, 25 Mar 2020 10:10:49 +0000	[thread overview]
Message-ID: <1d61fcc9546dee46769d7c15ddc75f86a596a5f0.camel@linuxfoundation.org> (raw)
In-Reply-To: <VE1PR04MB662103E59BAAF095702FC0DEE2CE0@VE1PR04MB6621.eurprd04.prod.outlook.com>

On Wed, 2020-03-25 at 01:33 +0000, Tom Hochstein wrote:
> > -----Original Message-----
> > From: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Sent: Tuesday, March 24, 2020 5:58 PM
> > To: Antoine Manache <a.manache@gmail.com>; Tom Hochstein <
> > tom.hochstein@nxp.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core][PATCH] security_flags.inc: fix flags missing
> > from SDK toolchain
> > 
> > I've therefore taken Tom's version with some tweaks to the commit
> > message.
> 
> Thanks. Can we get this on zeus? Do I need to cherry-pick and submit
> the patch?

Yes, please post it and then the stable maintainers can review it.

Cheers,

Richard


      reply	other threads:[~2020-03-25 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 17:02 [OE-core][PATCH] security_flags.inc: fix flags missing from SDK toolchain Tom Hochstein
2020-03-24 17:25 ` Antoine Manache
2020-03-24 18:03   ` Richard Purdie
2020-03-24 18:34     ` Tom Hochstein
2020-03-24 19:06       ` Antoine Manache
2020-03-24 22:57         ` Richard Purdie
2020-03-25  1:33           ` Tom Hochstein
2020-03-25 10:10             ` Richard Purdie [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=1d61fcc9546dee46769d7c15ddc75f86a596a5f0.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=a.manache@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tom.hochstein@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