All of 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:54:23 -0800	[thread overview]
Message-ID: <50A2C18F.8090303@zankel.net> (raw)
In-Reply-To: <20121113224442.70f141be@skate>

Hi Thomas,

On 11/13/2012 01:44 PM, Thomas Petazzoni wrote:
> Chris,
>
> On Tue, 13 Nov 2012 13:01:03 -0800, Chris Zankel wrote:
>
>> 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...
> You can keep your patch as is wrt to Config.in. What I propose to do is
> that I merge your Xtensa support in one of my branch together with my
> reorganization of the architecture definitions and I send a
> pull-request for the whole thing to Peter.
>
> Would that be OK for you?
That would be great! Could you please use v4 of the two patches as they
include changes suggested by Arnout.

Thanks,
-Chris

      reply	other threads:[~2012-11-13 21:54 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
2012-11-13 21:44             ` Thomas Petazzoni
2012-11-13 21:54               ` Chris Zankel [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=50A2C18F.8090303@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.