From: Chris Metcalf <cmetcalf@tilera.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>,
<linux-xtensa@linux-xtensa.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch: remove KCORE_ELF again
Date: Fri, 22 Mar 2013 16:05:22 -0400 [thread overview]
Message-ID: <514CB982.8070206@tilera.com> (raw)
In-Reply-To: <1363982392.1390.181.camel@x61.thuisdomein>
On 3/22/2013 3:59 PM, Paul Bolle wrote:
> On Fri, 2013-03-22 at 15:44 -0400, Chris Metcalf wrote:
>> I took the tile part of this patch into the tile tree. Thanks!
> Should I (try to) remember to send future patches for tile, if any,
> separately?
I think it's generally slightly easier for the arch maintainers to take changes that are just for their own arch, but it's not too hard to split out the per-arch piece, either.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
prev parent reply other threads:[~2013-03-22 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 0:40 [PATCH] arch: remove KCORE_ELF again Paul Bolle
2013-03-22 19:44 ` Chris Metcalf
2013-03-22 19:55 ` Max Filippov
2013-03-22 19:59 ` Paul Bolle
2013-03-22 20:05 ` Chris Metcalf [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=514CB982.8070206@tilera.com \
--to=cmetcalf@tilera.com \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=pebolle@tiscali.nl \
/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.