Separating driver and documentation changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi
I'm going to send a patch that extends existing driver with support for a new
variant of the existing device. The changes in the drivr code are rather
small, around 100 lines of code. Apart from the driver changes I
would like to also update Documentation/devicetree/bindings for this
driver to add the information about the new supported variant. Should I
split the changes and send them separately? If so, how can I make sure
that the documentation changes won't be merged to kernel source tree
until the drive's modifications are merged? (if ofc maintainer decides
to integrate them).

Best regards 
Patryk

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]

  Powered by Linux