Remove check for epoch on the receiver side, as this is a race condition between message arrival, and because we'll be still blocking in a synchronization call, is of no consequence to the user. We do an epoch check on the sending side,

so this isn't an issue there either.  Refs trac:488

This commit was SVN r12675.

The following Trac tickets were found above:
  Ticket 488 --> https://svn.open-mpi.org/trac/ompi/ticket/488

ompi/mca/osc/rdma/osc_rdma_component.c

@@ -474,10 +474,6 @@ ompi_osc_rdma_component_fragment_cb(struct mca_btl_base_module_t *btl,
                                       OMPI_WIN_FENCE | 
                                       OMPI_WIN_ACCESS_EPOCH |
                                       OMPI_WIN_EXPOSE_EPOCH);
-                } else {
-                    opal_output(0, "Invalid MPI_PUT on Window %s.  Window not in exposure epoch",
-                                module->p2p_win->w_name);
-                    break;
                 }
             }
 
@@ -511,10 +507,6 @@ ompi_osc_rdma_component_fragment_cb(struct mca_btl_base_module_t *btl,
                                       OMPI_WIN_FENCE | 
                                       OMPI_WIN_ACCESS_EPOCH |
                                       OMPI_WIN_EXPOSE_EPOCH);
-                } else {
-                    opal_output(0, "Invalid MPI_ACCUMULATE on Window %s.  Window not in exposure epoch",
-                                module->p2p_win->w_name);
-                    break;
                 }
             }
 
@@ -552,10 +544,6 @@ ompi_osc_rdma_component_fragment_cb(struct mca_btl_base_module_t *btl,
                                       OMPI_WIN_FENCE | 
                                       OMPI_WIN_ACCESS_EPOCH |
                                       OMPI_WIN_EXPOSE_EPOCH);
-                } else {
-                    opal_output(0, "Invalid MPI_GET on Window %s.  Window not in exposure epoch",
-                                module->p2p_win->w_name);
-                    break;
                 }
             }