Re: [PATCH 0/2] Fix illegal simplification of volatile stores

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Nov 12, 2017 at 6:59 AM, Luc Van Oostenryck
<luc.vanoostenryck@xxxxxxxxx> wrote:
> On Sun, Nov 12, 2017 at 01:29:08AM +0800, Christopher Li wrote:
>
> If you would do that:
> 1) it would be equivalent to rebasing one of my branches
> 2) it make me wonder if I have misunderstood something to the way
>    we had, some months ago, agreed to work together.

Just asking. Because you start to send patches like the build
series I don't intend to apply. I need to know it fall into the same
category.

> 3) it make me wonder why there is 67 branches in my github
>    tree waiting for you to pull them, most having been totally
>    ignored by you, a good number of them being 7 or 8 months old
>    with a few even older (not talking about the dozens of other
>    topic branches that I've never bothered to submit because they
>    don't make sense without their parent branches).

Hey, I assume you mean the llvm fix series.

We have agreement that will resume the pull again after the 5.0.1.
Which means right now. That series I just send out one important
feed back about the OP_PUSH. I thought I have send that one out
but I just find out it haven't. That is my bad.

Once we finalize a solution for that, that series is pull-able.

Please response to that email.

> 4) it make me wonder why this sudden promptitude from your part.
>

I am confused and need some clarification as well.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux