On 27/03/17 23:22, Luc Van Oostenryck wrote: > On Mon, Mar 27, 2017 at 10:56:52PM +0100, Ramsay Jones wrote: >> On 27/03/17 18:33, Luc Van Oostenryck wrote: >>> This serie contains preparatory patches for >>> sparse-llvm's fixes but not sparse-llvm specific >>> and having some values of their own. >>> >>> These patches were extracted from a previous >>> serie containing also the sparse-llvm patches. >>> >>> Changes since v5: >>> - use a table for compare_opcode() & swap_compare_opcode() >>> - fix test cases on 32bit machines >> >> Hmm, I assumed that this series should apply to master, and then >> the following 52 patch series on top. > > Well no, sorry. > I haven't explained because I thought it was obvious but > of course, it's not obvious at all. ;-) > These series apply, and in general any patches or series I send, > in the order I send them, on top of the stable part of sparse-next. > And by "the stable part of sparse-next" I mean that if sparse-next > contains serie-xyz-v2 and I sent serie-xyz-v3, the serie will apply > at the same place that the -v2 serie was. Hmm, OK. I assume Christopher knows what this means! So, I will wait for Christopher to re-integrate these patches and re-write the 'sparse-next' branch in the public repository before testing again. Thanks! ATB, Ramsay Jones -- 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
