incoming
Andrew Morton
maintainer- A few y2038 fixes which missed the merge window whiole dependencies in NFS were being sorted out.
- A bunch of fixes. Some minor, some not.
Subsystems affected by this patch series:
Arnd Bergmann <[email protected]>:
y2038: remove ktime to/from timespec/timeval conversion
y2038: remove unused time32 interfaces
y2038: hide timeval/timespec/itimerval/itimerspec types
Ioanna Alifieraki <[email protected]>:
Revert "ipc,sem: remove uneeded sem_undo_list lock usage in exit_sem()"
Christian Borntraeger <[email protected]>:
include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for swap
SeongJae Park <[email protected]>:
selftests/vm: add missed tests in run_vmtests
Joe Perches <[email protected]>:
get_maintainer: remove uses of P: for maintainer name
Douglas Anderson <[email protected]>:
scripts/get_maintainer.pl: deprioritize old Fixes: addresses
Christoph Hellwig <[email protected]>:
mm/swapfile.c: fix a comment in sys_swapon()
Vasily Averin <[email protected]>:
mm/memcontrol.c: lost css_put in memcg_expand_shrinker_maps()
Alexandru Ardelean <[email protected]>:
lib/string.c: update match_string() doc-strings with correct behavior
Gavin Shan <[email protected]>:
mm/vmscan.c: don't round up scan size for online memory cgroup
Wei Yang <[email protected]>:
mm/sparsemem: pfn_to_page is not valid yet on SPARSEMEM
Alexander Potapenko <[email protected]>:
lib/stackdepot.c: fix global out-of-bounds in stack_slabs
Randy Dunlap <[email protected]>:
MAINTAINERS: use tabs for SAFESETID
MAINTAINERS | 8 - include/linux/compat.h | 29 ------ include/linux/ktime.h | 37 ------- include/linux/time32.h | 154 --------------------------------- include/linux/timekeeping32.h | 32 ------ include/linux/types.h | 5 - include/uapi/asm-generic/posix_types.h | 2 include/uapi/linux/swab.h | 4 include/uapi/linux/time.h | 22 ++-- ipc/sem.c | 6 - kernel/compat.c | 64 ------------- kernel/time/time.c | 43 --------- lib/stackdepot.c | 8 + lib/string.c | 16 +++ mm/memcontrol.c | 4 mm/sparse.c | 2 mm/swapfile.c | 2 mm/vmscan.c | 9 + scripts/get_maintainer.pl | 32 ------ tools/testing/selftests/vm/run_vmtests | 33 +++++++ 20 files changed, 93 insertions(+), 419 deletions(-)
Andrew Morton
maintainerQuoted 4 lines · On Thu, 20 Feb 2020 20:00:30 -0800 Andrew Morton <[email protected]>…
- A few y2038 fixes which missed the merge window whiole dependencies in NFS were being sorted out.
- A bunch of fixes. Some minor, some not.
15 patches, based on ca7e1fd1026c5af6a533b4b5447e1d2f153e28f2
Quoted 5 lines · Andrew Morton
- A few y2038 fixes which missed the merge window whiole dependencies in NFS were being sorted out.
- A bunch of fixes. Some minor, some not.
Hmm. Konstantin's nice lore script _used_ to pick up your patches, but now they don't.
I'm not sure what changed. It worked with your big series of 118 patches.
It doesn't work with this smaller series of fixes.
I think the difference is that you've done something bad to your patch sending. That big series was properly threaded with each of the patches being a reply to the 'incoming' message.
This series is not.
Please, Andrew, can you make your email flow more consistent so that I can actually use the nice new tool to download a patch series?
Linus
Quoted 12 lines · Linus Torvalds
Quoted 5 lines · Andrew Morton
- A few y2038 fixes which missed the merge window whiole dependencies in NFS were being sorted out.
- A bunch of fixes. Some minor, some not.
Hmm. Konstantin's nice lore script _used_ to pick up your patches, but now they don't.
I'm not sure what changed. It worked with your big series of 118 patches.
Quoted 7 lines
It doesn't work with this smaller series of fixes.
I think the difference is that you've done something bad to your patch sending. That big series was properly threaded with each of the patches being a reply to the 'incoming' message.
This series is not.
This is correct -- each patch is posted without an in-reply-to, so public-inbox doesn't group them into a thread.
E.g.:
https://lore.kernel.org/linux-mm/20200221040350.84HaG%[email protected]/
Quoted 3 lines
Please, Andrew, can you make your email flow more consistent so that I can actually use the nice new tool to download a patch series?
Andrew, I'll be happy to provide you with a helper tool if you can describe me your workflow. E.g. if you have a quilt directory of patches plus a series file, it could easily be a tiny wrapper like:
send-patches --base-commit 1234abcd --cover cover.txt patchdir/series
-K
Quoted 28 lines · Konstantin Ryabitsev
Quoted 12 lines · Linus Torvalds
Quoted 5 lines · Andrew Morton
- A few y2038 fixes which missed the merge window whiole dependencies in NFS were being sorted out.
- A bunch of fixes. Some minor, some not.
Hmm. Konstantin's nice lore script _used_ to pick up your patches, but now they don't.
I'm not sure what changed. It worked with your big series of 118 patches.
Quoted 7 lines
It doesn't work with this smaller series of fixes.
I think the difference is that you've done something bad to your patch sending. That big series was properly threaded with each of the patches being a reply to the 'incoming' message.
This series is not.
This is correct -- each patch is posted without an in-reply-to, so public-inbox doesn't group them into a thread.
E.g.:
https://lore.kernel.org/linux-mm/20200221040350.84HaG%[email protected]/Quoted 1 line
Quoted 8 lines
Quoted 2 lines
Please, Andrew, can you make your email flow more consistent so that I can actually use the nice new tool to download a patch series?
Andrew, I'll be happy to provide you with a helper tool if you can describe me your workflow. E.g. if you have a quilt directory of patches plus a series file, it could easily be a tiny wrapper like:
send-patches --base-commit
1234abcd--cover cover.txt patchdir/series
Once/if there is such tool, could it perhaps instead of mass e-mailing create git commits, push them to korg repo and send a pull request?
Thanks,
Vlastimil
Quoted 2 lines
-K
Side note: I've obviously picked it up the old-fashioned way, but I had been looking forward to seeing if I could just automate this more.
Linus
Quoted 5 lines · Linus Torvalds
Please, Andrew, can you make your email flow more consistent so that I can actually use the nice new tool to download a patch series?
Linus