You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, although this shows why rustc should not need to have the target to begin with. Unless there is a reason not to, it is cleaner to have it on our end. That eliminates a dependency on a common name, resolves the "naming dispute" FIXME and avoids rustc having to track all possible targets out there. It seems like they might agree, so I supported that view in rust-lang/rust#74247
It was obsoleted by #28 given we use custom targets, although I didn't close this given the discussions are ongoing e.g. see the overview I wrote yesterday at rust-lang/rust#71009. But changing the title or closing this and creating a new issue makes sense.
Activity
ojeda commentedon Oct 14, 2020
Yeah, although this shows why rustc should not need to have the target to begin with. Unless there is a reason not to, it is cleaner to have it on our end. That eliminates a dependency on a common name, resolves the "naming dispute" FIXME and avoids rustc having to track all possible targets out there. It seems like they might agree, so I supported that view in rust-lang/rust#74247
Ericson2314 commentedon Oct 15, 2020
I'm in now way official over there, to be clear, but yes you state my view exactly! I don't think these sorts of layer violations help anyone.
ojeda commentedon Nov 26, 2020
In #28 I go the route of having our own target spec.
mm: replace memmap_context by meminit_context
mm: don't rely on system state to detect hot-plug operations
alex commentedon Jan 21, 2021
@ojeda was this obsoleted by the switch to not use cargo?
ojeda commentedon Jan 21, 2021
It was obsoleted by #28 given we use custom targets, although I didn't close this given the discussions are ongoing e.g. see the overview I wrote yesterday at rust-lang/rust#71009. But changing the title or closing this and creating a new issue makes sense.
alex commentedon Jan 22, 2021
I'm going to close this, given the precise original reason I filed it for has been obviated.
x86/kvm: Fix broken irq restoration in kvm_wait
veth: ensure skb entering GRO are not cloned.
1 remaining item
ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS
nvme-tcp: fix possible circular locking when deleting a controller un…
cifs: fix use-after-free caused by invalid pointer `hostname`
scsi: megaraid_sas: Fix deadlock on firmware crashdump
arm64: patching: fix handling of execmem addresses
ionic: fix kernel panic due to multi-buffer handling
cachefiles: fix dentry leak in cachefiles_open_file()
HID: wacom: fix when get product name maybe null pointer
drm/msm: Fix refcnt underflow in error path
drm/msm: Fix submit error path cleanup
drm/amdgpu: Fix general protection fault in amdgpu_vm_bo_reset_state_…
btrfs: fix block_group_tree dirty_list corruption
btrfs: fix block_group_tree dirty_list corruption
btrfs: fix block_group_tree dirty_list corruption
btrfs: fix block_group_tree dirty_list corruption