tech-kern by thread

• Date Index
• Date Index (newest page)
• Old Index

• GENERIC Kernel Build errors with -fsanitize=undefi, Harry Pantazis
  • Re: GENERIC Kernel Build errors with -fsanitize=un, Kamil Rytarowski
    • Re: GENERIC Kernel Build errors with -fsanitize=un, Harry Pantazis
      • Re: GENERIC Kernel Build errors with -fsanitize=un, Christos Zoulas
      • Re: GENERIC Kernel Build errors with -fsanitize=un, Robert Elz
      • Re: GENERIC Kernel Build errors with -fsanitize=un, Christos Zoulas
      • ./build.sh -k feature request (was Re: GENERIC Ker, Reinoud Zandijk
      • Re: ./build.sh -k feature request (was Re: GENERIC, Reinoud Zandijk
      • Re: ./build.sh -k feature request (was Re: GENERIC, Reinoud Zandijk
      • Re: ./build.sh -k feature request (was Re: GENERIC, Greg Troxel
      • Re: ./build.sh -k feature request (was Re: GENERIC, Mouse
      • Re: ./build.sh -k feature request (was Re: GENERIC, Joerg Sonnenberger
      • Re: ./build.sh -k feature request (was Re: GENERIC, Mouse
      • Re: ./build.sh -k feature request (was Re: GENERIC, Kamil Rytarowski
      • Re: ./build.sh -k feature request (was Re: GENERIC, Reinoud Zandijk
      • Re: ./build.sh -k feature request (was Re: GENERIC, Kamil Rytarowski
      • Re: ./build.sh -k feature request (was Re: GENERIC, Martin Husemann
      • re: ./build.sh -k feature request (was Re: GENERIC, matthew green
    • Re: GENERIC Kernel Build errors with -fsanitize=un, Robert Elz
• i2c and indirect vs. direct config, Martin Husemann
  • Re: i2c and indirect vs. direct config, Michael
  • Re: i2c and indirect vs. direct config, Jason Thorpe
    • Re: i2c and indirect vs. direct config, Greg Troxel
      • Re: i2c and indirect vs. direct config, Mouse
      • Re: i2c and indirect vs. direct config, Brad Spencer
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Brad Spencer
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Brad Spencer
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Brad Spencer
      • Re: i2c and indirect vs. direct config, Paul Goyette
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Paul Goyette
      • Re: i2c and indirect vs. direct config, Paul Goyette
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Thor Lancelot Simon
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Martin Husemann
      • Re: i2c and indirect vs. direct config, Paul Goyette
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Jason Thorpe
      • Re: i2c and indirect vs. direct config, Paul Goyette
      • Re: i2c and indirect vs. direct config, Rhialto
      • Re: i2c and indirect vs. direct config, Paul Goyette
      • Re: i2c and indirect vs. direct config, Michael
• PR kern/52468, glitch
• PWM and user space API, Jason Thorpe
  • Re: PWM and user space API, Jason Thorpe
    • Re: PWM and user space API, Jason Thorpe
  • Re: PWM and user space API, Jared McNeill
  • Re: PWM and user space API, Robert Swindells
• Asymmetric Disk I/O priorities in a RAIDframe RAID, Hauke Fath
  • Re: Asymmetric Disk I/O priorities in a RAIDframe , Greg Oster
• Audio update pertaining to mixer devices and hw.dr, Nathanial Sloss
  • Re: Audio update pertaining to mixer devices and h, Paul Goyette
  • re: Audio update pertaining to mixer devices and h, matthew green
• QEMU/NetBSD status wiki page, Kamil Rytarowski
  • Re: QEMU/NetBSD status wiki page, Warner Losh
    • Re: QEMU/NetBSD status wiki page, Kamil Rytarowski
      • Re: QEMU/NetBSD status wiki page, Warner Losh
      • Re: QEMU/NetBSD status wiki page, Kamil Rytarowski
• cpu1: failed to start (amd64), Michael Taylor
  • Re: cpu1: failed to start (amd64), Michael Taylor
    • Re: cpu1: failed to start (amd64), Greg Troxel
• Revisiting uvm_loan() for 'direct' write pipes, Jaromír Doleček
  • Re: Revisiting uvm_loan() for 'direct' write pipes, Jaromír Doleček
    • Re: Revisiting uvm_loan() for 'direct' write pipes, Jason Thorpe
    • Re: Revisiting uvm_loan() for 'direct' write pipes, Thor Lancelot Simon
  • Re: Revisiting uvm_loan() for 'direct' write pipes, Jason Thorpe
    • Re: Revisiting uvm_loan() for 'direct' write pipes, Jaromír Doleček
• Ambient light sensors in envsys, Jason Thorpe
  • Re: Ambient light sensors in envsys, Jason Thorpe
  • Re: Ambient light sensors in envsys, maya
    • Re: Ambient light sensors in envsys, Michael
• FIOSETOWN and TIOCSPGRP vs control ttys, Mouse
  • Re: FIOSETOWN and TIOCSPGRP vs control ttys, Christos Zoulas
• firefox sandboxing, Thomas Klausner
  • Re: firefox sandboxing, Rhialto
  • Re: firefox sandboxing, Jason Thorpe
• Removing uvm_emap (aka ephemeral mapping interface, Jaromír Doleček
• GSoC 2018, Marwa Desouky
  • Re: GSoC 2018, Radoslaw Kujawa
• kern/53166: NFS default to UDP; it should really d, Jason Thorpe
  • Re: kern/53166: NFS default to UDP; it should real, Jason Thorpe
• NetBSD Audio specification 2018, Nathanial Sloss
  • Re: NetBSD Audio specification 2018, Nathanial Sloss
    • Re: NetBSD Audio specification 2018, Nathanial Sloss
• bwfm(4) PCI support, coypu
• Kernel module framework status?, Anders Magnusson
  • Re: Kernel module framework status?, Paul Goyette
    • Re: Kernel module framework status?, Anders Magnusson
  • Re: Kernel module framework status?, John Nemeth
    • Re: Kernel module framework status?, Mouse
      • Re: Kernel module framework status?, John Nemeth
      • re: Kernel module framework status?, matthew green
      • re: Kernel module framework status?, Eduardo Horvath
      • Re: Kernel module framework status?, maya
      • Re: Kernel module framework status?, Warner Losh
      • Re: Kernel module framework status?, John Nemeth
      • Re: Kernel module framework status?, Warner Losh
      • Re: Kernel module framework status?, Warner Losh