From: Greg KH <greg@kroah.com>
To: Patryk Biel <pbiel7@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Separating driver and documentation changes
Date: Thu, 22 Aug 2024 17:12:02 +0800 [thread overview]
Message-ID: <2024082218-exemplify-collected-ae2f@gregkh> (raw)
In-Reply-To: <20240822082932.vlovfb2wfzkpy2dv@LAP470330.localdomain>
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
prev parent reply other threads:[~2024-08-22 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 8:29 Separating driver and documentation changes Patryk Biel
2024-08-22 9:12 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024082218-exemplify-collected-ae2f@gregkh \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=pbiel7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox