On Tue, Jun 07, 2022 at 02:14:32PM +0200, Thomas Gleixner wrote: > On Tue, Jun 07 2022 at 12:58, Greg KH wrote: > > On Mon, Jun 06, 2022 at 10:10:17PM +0200, Thomas Gleixner wrote: > >> --- > >> Documentation/driver-api/vfio-mediated-device.rst | 4 +--- > >> arch/arm/boot/bootp/bootp.lds | 5 +---- > >> include/linux/input/elan-i2c-ids.h | 5 +---- > >> 3 files changed, 3 insertions(+), 11 deletions(-) > > > > I understand the goal to split this up per "rule", but that rule name > > makes no sense to any kernel developer. They don't know what it is, or > > where it came from, or anything else like that. > > I was just reusing the scripts/approach from 3 years ago :) Ah, forgot about that. Nevermind then :) > > This also touches files across subsystems, generally not a good idea. > > Is your goal to get acks from the people here and then split them up > > per-subsystem later, or are you thinking you want these merged as-is? > > I assumed that we merge that through your spdx tree. Though it might be > not the worst idea to route them through the maintainers, so they become > more aware of the overall problem. Through the spdx tree is probably simplest as these are all for older files that almost never get touched. And if they do, this is the top of the file so merge conflicts should be non-existent. thanks, greg k-h
