Hello, Bartlomiej. Bartlomiej Zolnierkiewicz wrote: > Good question, how's about: > > Once tj/block-unify-sector-and-data_len is in block/for-2.6.31 and your tree > is ready I will pull it into the separate branch. This branch can be then > pulled into ide/for-next or into new ide/all branch (replacing ide/for-next > in linux-next). > > This means that I'll have to synchronize merge window merges with Jens but > this is needed already and shouldn't be a problem. > > If somebody [ Tejun/Jens: I'm talking to you :) ] has a better idea how to > handle this please stand-up. There needs to be a sync point anyway and there's one more patchset on top of block-unify-sector-and-data_len involving ide changes (the block-peek-fetch one), so if both get acked by Jens, it would be easier to simply branch out from there. From there on, I don't expect too much disruption to ide from further block layer changes, so things should be okay. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
