git: d56be4992dc7 - stable/13 - linux(4): Drop a weird comment from linux_set_syscall_retval on amd64

The branch stable/13 has been updated by dchagin:

URL: https://cgit.FreeBSD.org/src/commit/?id=d56be4992dc753bc08c10223996501be46aceb64

commit d56be4992dc753bc08c10223996501be46aceb64
Author:     Dmitry Chagin <dchagin@FreeBSD.org>
AuthorDate: 2023-05-28 14:05:44 +0000
Commit:     Dmitry Chagin <dchagin@FreeBSD.org>
CommitDate: 2023-06-29 08:16:01 +0000

    linux(4): Drop a weird comment from linux_set_syscall_retval on amd64
    
    I agree, it would be great to avoid PCB_FULL_IRET, however we should
    follow Linux system call ABI.
    
    Reviewed by:            emaste
    Differential Revision:  https://reviews.freebsd.org/D40152
    MFC after:              1 month
    
    (cherry picked from commit a99b890ecd26131e0c91e5693b55f5700c40a847)
---
 sys/amd64/linux/linux_sysvec.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/sys/amd64/linux/linux_sysvec.c b/sys/amd64/linux/linux_sysvec.c
index 5e7bc96d0148..f43e7d3a02bc 100644
--- a/sys/amd64/linux/linux_sysvec.c
+++ b/sys/amd64/linux/linux_sysvec.c
@@ -191,9 +191,6 @@ linux_set_syscall_retval(struct thread *td, int error)
 	 * and %r11 values are not preserved across the syscall.
 	 * Require full context restore to get all registers except
 	 * those two restored at return to usermode.
-	 *
-	 * XXX: Would be great to be able to avoid PCB_FULL_IRET
-	 *      for the error == 0 case.
 	 */
 	set_pcb_flags(td->td_pcb, PCB_FULL_IRET);
 }