Re: linux-next: block tree build failure
From: Martin K. Petersen
Date: Mon May 25 2009 - 01:39:18 EST
>>>>> "Stephen" == Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> writes:
Stephen> Caused by commit 025146e13b63483add912706c101fb0fb6f015cc
Stephen> ("block: Move queue limits to an embedded struct") from the
Stephen> block tree interacting with commit
Stephen> ("dm-avoid-unsupported-spanning-of-md-stripe-boundaries") from
Stephen> the device-mapper tree.
Stephen> This is caused by commit
Stephen> e1defc4ff0cf57aca6c5e3ff99fa503f5943c1f1 ("block: Do away with
Stephen> the notion of hardsect_size") from the block tree interacting
Stephen> with commits cc1018ae8a413b595a1f0f822928dd9e81a75e59
Stephen> ("dm-table-ensure-targets-are-aligned-to-hardsect_size") and
Stephen> ("dm-table-validate-device-hardsect_size") from the
Stephen> device-mapper tree.
Bummer. I wasn't aware Alasdair had taken those patches into his DM tree
yet. I thought he was waiting for my block layer patches to land.
The accessor function patch in my patch series was explicitly put in
place to enable changing the API without affecting users. And we've
tried to be careful about staging these patches in the right order
throughout all the involved trees.
Sorry about the slip-up :|
Martin K. Petersen Oracle Linux Engineering
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/