From: taras.kondratiuk@linaro•org (Taras Kondratiuk)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: kprobes: big-endian support
Date: Fri, 28 Mar 2014 20:13:05 +0200 [thread overview]
Message-ID: <5335BBB1.60402@linaro.org> (raw)
In-Reply-To: <20140328112841.GF7528@n2100.arm.linux.org.uk>
On 03/28/2014 01:28 PM, Russell King - ARM Linux wrote:
> On Wed, Mar 26, 2014 at 12:26:34PM +0200, Taras Kondratiuk wrote:
>> On 02/20/2014 12:59 AM, Taras Kondratiuk wrote:
>>
>> Hi Russell,
>>
>> Is there any issue with this pull request?
>> Should I do something to get it pulled?
>
> There's nothing wrong, apart from me being far too busy hacking on really
> crap code to care about reading much email - which means that lots of
> email simply just gets buried and lost.
>
> There is now a problem with this pull - it conflicts very badly with Dave
> Long's uprobes code, which I've already pulled, so much so that I'm not
> happy to do the conflict resolution since I know nothing about this code,
> and it's a feature I don't make any use of.
I've rebased it onto your for-next branch. Kprobes are functional
in LE and BE. I'll send an updated pull request after verifying uprobes.
> I notice that Dave Long and yourself are both under the Linaro umbrella,
> but there seems to be no coordination between yourselves, despite working
> on the same code...
Yeah, we are working in different teams and unfortunately haven't coordinated
an upstreaming sequence.
--
Taras Kondratiuk
next prev parent reply other threads:[~2014-03-28 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 12:09 [GIT PULL] ARM: kprobes: big-endian support Taras Kondratiuk
2014-02-19 22:59 ` Taras Kondratiuk
2014-03-26 10:26 ` Taras Kondratiuk
2014-03-28 11:28 ` Russell King - ARM Linux
2014-03-28 18:13 ` Taras Kondratiuk [this message]
2014-03-28 18:22 ` Russell King - ARM Linux
2014-03-28 21:43 ` Taras Kondratiuk
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=5335BBB1.60402@linaro.org \
--to=taras.kondratiuk@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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