From: Max Filippov <jcmvbkbc@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "augustine.sterling@gmail.com" <augustine.sterling@gmail.com>,
binutils@sourceware.org, gdb-patches@sourceware.org,
David Weatherford <weath@cadence.com>,
Maxim Grigoriev <maxim2405@gmail.com>,
Woody LaRue <larue@cadence.com>
Subject: Re: [RFC 2/5] xtensa: make configuration dynamic
Date: Wed, 07 Jun 2017 19:13:00 -0000 [thread overview]
Message-ID: <CAMo8BfLumrfePK7aoiDGntiw2fufR7JasyPiU72ig0PFHmRbFQ@mail.gmail.com> (raw)
In-Reply-To: <3e6148ad-a559-5aac-da17-ddf4a7bb5e36@redhat.com>
Hi Nick,
On Tue, Jun 6, 2017 at 5:53 AM, Nick Clifton <nickc@redhat.com> wrote:
> Well the binutils already has a plugin support, so this patch is just
> adding the ability for a different type of plugin to be used. I am OK
> with that, providing that the plugin itself is also licensed under the
> GPL v3.
Yes, that's the intention. I've also got a suggestion on the gcc list to add
a mechanism that makes the plugin license requirement more apparent,
I'll do it in the next iteration of this series.
--
Thanks.
-- Max
next prev parent reply other threads:[~2017-06-07 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 21:12 [RFC 0/5] xtensa: support dynamic configuration Max Filippov
2017-05-22 21:12 ` [RFC 3/5] xtensa: support dynconfig on windows Max Filippov
2017-06-12 15:45 ` Nick Clifton
2017-05-22 21:12 ` [RFC 2/5] xtensa: make configuration dynamic Max Filippov
2017-05-26 18:10 ` augustine.sterling
2017-05-26 18:15 ` augustine.sterling
2017-06-06 12:53 ` Nick Clifton
2017-06-07 19:13 ` Max Filippov [this message]
2017-05-22 21:12 ` [RFC 1/5] xtensa: don't expect XCHAL_* macros to be constant Max Filippov
2017-05-26 17:36 ` augustine.sterling
2017-05-22 21:13 ` [RFC 4/5] xtensa: make xtensa_modules dynamic Max Filippov
2017-06-12 15:49 ` Nick Clifton
2017-05-22 21:13 ` [RFC 5/5] gdb: xtensa: make tdep and linux-nat dynamically configurable Max Filippov
2017-06-06 12:41 ` [RFC 0/5] xtensa: support dynamic configuration Nick Clifton
2017-06-07 19:23 ` Max Filippov
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=CAMo8BfLumrfePK7aoiDGntiw2fufR7JasyPiU72ig0PFHmRbFQ@mail.gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=augustine.sterling@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=larue@cadence.com \
--cc=maxim2405@gmail.com \
--cc=nickc@redhat.com \
--cc=weath@cadence.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