Searched hist:17973 (Results 1 - 4 of 4) sorted by relevance
| /linux-master/arch/arm64/boot/dts/xilinx/ | ||
| H A D | zynqmp-zcu106-revA.dts | diff f4be206c Mon Jun 14 09:25:32 MDT 2021 Michal Simek <michal.simek@xilinx.com> arm64: zynqmp: Remove information about dma clock on zcu106 Clock setting is not static anymore that's why it depends on firmware setup that's why remove this comment. Signed-off-by: Michal Simek <michal.simek@xilinx.com> Link: https://lore.kernel.org/r/17973ffda4e163a4b89d4732fe6fc7e089962ae7.1623684253.git.michal.simek@xilinx.com |
| /linux-master/scripts/dtc/include-prefixes/arm64/xilinx/ | ||
| H A D | zynqmp-zcu106-revA.dts | diff f4be206c Mon Jun 14 09:25:32 MDT 2021 Michal Simek <michal.simek@xilinx.com> arm64: zynqmp: Remove information about dma clock on zcu106 Clock setting is not static anymore that's why it depends on firmware setup that's why remove this comment. Signed-off-by: Michal Simek <michal.simek@xilinx.com> Link: https://lore.kernel.org/r/17973ffda4e163a4b89d4732fe6fc7e089962ae7.1623684253.git.michal.simek@xilinx.com |
| /linux-master/fs/reiserfs/ | ||
| H A D | file.c | diff 17973f5a Mon Jul 16 00:40:08 MDT 2007 Micah Cowan <micah@cowan.name> Only send SIGXFSZ when exceeding rlimits. Some users have been having problems with utilities like cp or dd dumping core when they try to copy a file that's too large for the destination filesystem (typically, > 4gb). Apparently, some defunct standards required SIGXFSZ to be sent in such circumstances, but SUS only requires/allows it for when a written file exceeds the process's resource limits. I'd like to limit SIGXFSZs to the bare minimum required by SUS. Patch sent per http://lkml.org/lkml/2007/4/10/302 Signed-off-by: Micah Cowan <micahcowan@ubuntu.com> Acked-by: Alan Cox <alan@redhat.com> Cc: <reiserfs-dev@namesys.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
| /linux-master/mm/ | ||
| H A D | filemap.c | diff 17973f5a Mon Jul 16 00:40:08 MDT 2007 Micah Cowan <micah@cowan.name> Only send SIGXFSZ when exceeding rlimits. Some users have been having problems with utilities like cp or dd dumping core when they try to copy a file that's too large for the destination filesystem (typically, > 4gb). Apparently, some defunct standards required SIGXFSZ to be sent in such circumstances, but SUS only requires/allows it for when a written file exceeds the process's resource limits. I'd like to limit SIGXFSZs to the bare minimum required by SUS. Patch sent per http://lkml.org/lkml/2007/4/10/302 Signed-off-by: Micah Cowan <micahcowan@ubuntu.com> Acked-by: Alan Cox <alan@redhat.com> Cc: <reiserfs-dev@namesys.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
Completed in 477 milliseconds