Separating driver and documentation changes

Separating driver and documentation changes

[Patryk Biel]

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@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Separating driver and documentation changes

[Greg KH]

On Thu, Aug 22, 2024 at 10:29:32AM +0200, Patryk Biel wrote:
> 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).

Make it a patch series, first patch does the bindings change and the
second does the driver change.  You will find thousands of examples of
people doing this on the development mailing lists, it's the preferred
way.

good luck!

greg k-h

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