linq styling, chaining where clause vs and operator

Is there a (logical/performance) difference to writing:

ATable.Where(x=> condition1 && condition2 && condition3)

or

ATable.Where(x=>condition1).Where(x=>condition2).Where(x=>condition3)

I've been using the former but realised that with the latter, I can read and copy parts of a query out to use somewhere else easier. Any thoughts?