Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v3] xtensa: support configurable processor configurations
Date: Tue, 13 Nov 2012 13:01:03 -0800	[thread overview]
Message-ID: <50A2B50F.60609@zankel.net> (raw)
In-Reply-To: <50A2ADBC.9080704@mind.be>

Hi Arnout,

Sorry, I got your email after I sent out version 4 of the patch, which
doesn't include the change you mentioned (somehow, fetchmail was stuck
:-( So, please let me know if you want me to send out another version
that includes that change. I don't want to confuse Thomas with all those
versions...

Thanks,
-Chris



On 11/13/2012 12:29 PM, Arnout Vandecappelle wrote:
>> I guess I don't understand what that patch does, i.e. where is the
>> 'if...endif'? Could you maybe point to the patch?
>   I'm talking about http://patchwork.ozlabs.org/patch/196916/
> In arch/Config.in, it introduces the following construct:
>
> if BR2_xtensa
> source "arch/Config.in.xtensa"
> endif
>
>   This removes the need for adding 'depend on BR2_xtensa' in every config
> option in that file.
>
>   It's true that _now_ xtensa would be the only one using that scheme, but the
> idea is that if you do that for xtensa now, it will be easier to merge in
> Thomas's patch later (or vice versa, it will be easier to rebase your patch
> once Thomas's patch gets merged).

  reply	other threads:[~2012-11-13 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10  0:20 [Buildroot] [PATCH 2/2 v3] xtensa: support configurable processor configurations Chris Zankel
2012-11-10  0:51 ` Arnout Vandecappelle
2012-11-12 21:28   ` Chris Zankel
2012-11-12 21:33     ` Arnout Vandecappelle
2012-11-12 23:45       ` Chris Zankel
2012-11-13 20:29         ` Arnout Vandecappelle
2012-11-13 21:01           ` Chris Zankel [this message]
2012-11-13 21:44             ` Thomas Petazzoni
2012-11-13 21:54               ` Chris Zankel

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=50A2B50F.60609@zankel.net \
    --to=chris@zankel.net \
    --cc=buildroot@busybox.net \
    /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