Skip site navigation (1)Skip section navigation (2)

2019/freebsd-current/20190707.freebsd-current

Messages: 43, sorted by subject
Last update: Mon Feb 13 14:17:13 UTC 2023

home | up | archive sorted by: subject | author | date | reverse date
  1. Jul  5 Rick Macklem               Re: [Differential] D20584: add a linux compatible copy_file_range(2) syscall
  2. Jul  5 Alan Somers                 Re: [Differential] D20584: add a linux compatible copy_file_range(2) syscall
  3. Jul  1 Edward Tomasz =?utf-8?Q?Na Call for 2019Q2 quarterly status reports
  4. Jul  1 Andriy Gapon               i2c bit banging timeout for SCL
  5. Jul  1 Poul-Henning Kamp           Re: i2c bit banging timeout for SCL
  6. Jul  1 Andriy Gapon                Re: i2c bit banging timeout for SCL
  7. Jul  1 Ian Lepore                  Re: i2c bit banging timeout for SCL
  8. Jul  1 Warner Losh                 Re: i2c bit banging timeout for SCL
  9. Jul  1 Poul-Henning Kamp           Re: i2c bit banging timeout for SCL
 10. Jul  1 Warner Losh                 Re: i2c bit banging timeout for SCL
 11. Jul  1 Ian Lepore                  Re: i2c bit banging timeout for SCL
 12. Jul  3 David Wolfskill            No keyboard or mouse for X11 after r349596 -> r349645 update
 13. Jul  3 David Wolfskill             Re: No keyboard or mouse for X11 after r349596 -> r349645 update
 14. Jul  5 Thomas Laus                Problem with USB after r349133
 15. Jul  5 Hans Petter Selasky         Re: Problem with USB after r349133
 16. Jul  6 Thomas Laus                 Re: Problem with USB after r349133
 17. Jul  6 Graham Perrin               Re: Problem with USB after r349133
 18. Jul  6 Thomas Laus                 Re: Problem with USB after r349133
 19. Jul  5 Rick Macklem               should a copy_file_range(2) syscall be interrupted via a signal
 20. Jul  5 Hans Petter Selasky         Re: should a copy_file_range(2) syscall be interrupted via a signal


21. Jul 5 Mark Johnston Re: should a copy_file_range(2) syscall be interrupted via a signal 22. Jul 5 Alan Somers Re: should a copy_file_range(2) syscall be interrupted via a signal 23. Jul 5 Rick Macklem Re: should a copy_file_range(2) syscall be interrupted via a signal 24. Jul 5 Rick Macklem Re: should a copy_file_range(2) syscall be interrupted via a signal 25. Jul 5 Jilles Tjoelker Re: should a copy_file_range(2) syscall be interrupted via a signal 26. Jul 5 Konstantin Belousov Re: should a copy_file_range(2) syscall be interrupted via a signal 27. Jul 5 Rick Macklem Re: should a copy_file_range(2) syscall be interrupted via a signal 28. Jul 5 Konstantin Belousov Re: should a copy_file_range(2) syscall be interrupted via a signal 29. Jul 6 Steve Kargl Someone broke USB 30. Jul 6 Hans Petter Selasky Re: Someone broke USB 31. Jul 6 Steve Kargl Re: Someone broke USB 32. Jul 6 Steve Kargl Re: Someone broke USB 33. Jul 6 Hans Petter Selasky Re: Someone broke USB 34. Jul 6 Steve Kargl Re: Someone broke USB 35. Jul 6 Ian Lepore Re: Someone broke USB 36. Jul 6 Hans Petter Selasky Re: Someone broke USB 37. Jul 6 Thomas Laus Re: Someone broke USB 38. Jul 6 Steve Kargl Re: Someone broke USB 39. Jul 5 Rick Macklem test program for copy_file_range(2) 40. Jul 5 Alan Somers Re: test program for copy_file_range(2)
41. Jul 5 Rick Macklem Re: test program for copy_file_range(2) 42. Jul 5 Alan Somers Re: test program for copy_file_range(2) 43. Jul 5 Rick Macklem Re: test program for copy_file_range(2)


home | up | archive sorted by: subject | author | date | reverse date