review: move comments

Signed-off-by: Dr. Jan-Philip Gehrcke <[email protected]>

Author: jgehrcke

cmd/compute-domain-kubelet-plugin/device_state.go

@@ -239,10 +239,10 @@ func (s *DeviceState) Unprepare(ctx context.Context, claimRef kubeletplugin.Name
 			claimRef.Name,
 			metav1.GetOptions{})
 
+		// TODO: distinguish errors -- if this is a 'not found' error then this
+		// is permanent and we may want to drop the claim from the checkpoint.
+		// Otherwise, this might be worth retrying?
 		if err != nil {
-			// TODO: distinguish errors -- if this is a 'not found' error then
-			// this is permanent and we may want to drop the claim from the
-			// checkpoint. Otherwise, this might be worth retrying?
 			return permanentError{fmt.Errorf("failed to fetch ResourceClaim %s: %w", claimRef.String(), err)}
 		}
 		if claim.Status.Allocation == nil {
@@ -261,10 +261,9 @@ func (s *DeviceState) Unprepare(ctx context.Context, claimRef kubeletplugin.Name
 		return fmt.Errorf("unsupported ClaimCheckpointState: %v", pc.CheckpointState)
 	}
 
+	// Assume that this is a retryable error. If there is any chance for this
+	// error to be permanent: drop the claim from checkpoint then regardless?
 	if err := s.cdi.DeleteClaimSpecFileIfExists(claimUID); err != nil {
-		// Assume that this is a retryable error. If there is any chance for
-		// this error to be permanent: drop the claim from checkpoint then
-		// regardless?
 		return fmt.Errorf("unable to delete CDI spec file for claim: %w", err)
 	}
 
@@ -294,7 +293,7 @@ func (s *DeviceState) getCheckpoint() (*Checkpoint, error) {
 // read-mutate-write sequence must be performed under a lock: we must be
 // conceptually certain that multiple read-mutate-write actions never overlap.
 // Currently, it is assumed that any caller gets here by first acquiring
-// driver's `pulock`.`
+// driver's `pulock`.
 func (s *DeviceState) updateCheckpoint(mutate func(*Checkpoint)) error {
 	checkpoint, err := s.getCheckpoint()
 	if err != nil {