diff options
author | Chris Metcalf <cmetcalf@tilera.com> | 2011-02-28 15:58:39 -0500 |
---|---|---|
committer | Chris Metcalf <cmetcalf@tilera.com> | 2011-03-10 13:14:03 -0500 |
commit | 5fb682b0644cd20015d9b0e3ca6921ad5533f4ba (patch) | |
tree | 0a2520197ebf92b6a27e69241bd4f242d1b39be3 /arch/tile/mm | |
parent | 00dce03134689a257120ae2aa18ba7d1a736bef7 (diff) |
arch/tile: fix some comments and whitespace
This is a grab bag of changes with no actual change to generated code.
This includes whitespace and comment typos, plus a couple of stale
comments being removed.
Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
Diffstat (limited to 'arch/tile/mm')
-rw-r--r-- | arch/tile/mm/fault.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/arch/tile/mm/fault.c b/arch/tile/mm/fault.c index dcebfc831cd6..758f597f488c 100644 --- a/arch/tile/mm/fault.c +++ b/arch/tile/mm/fault.c | |||
@@ -655,14 +655,6 @@ struct intvec_state do_page_fault_ics(struct pt_regs *regs, int fault_num, | |||
655 | } | 655 | } |
656 | 656 | ||
657 | /* | 657 | /* |
658 | * NOTE: the one other type of access that might bring us here | ||
659 | * are the memory ops in __tns_atomic_acquire/__tns_atomic_release, | ||
660 | * but we don't have to check specially for them since we can | ||
661 | * always safely return to the address of the fault and retry, | ||
662 | * since no separate atomic locks are involved. | ||
663 | */ | ||
664 | |||
665 | /* | ||
666 | * Now that we have released the atomic lock (if necessary), | 658 | * Now that we have released the atomic lock (if necessary), |
667 | * it's safe to spin if the PTE that caused the fault was migrating. | 659 | * it's safe to spin if the PTE that caused the fault was migrating. |
668 | */ | 660 | */ |