adding liveupdate tree to linux-next

Hi Mark,

We've setup a tree for Kexec HandOver/Live Update work and we are starting to take KHO/LUO and kexec/kdump patches via that tree.

Can you please add our branches to linux-next?

https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#fixes
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#next
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#kexec-fixes
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#kexec-next

Sincerely yours,
Mike.

I've added all of these from today (I see they're all at v7.0 for now, please note that we're in the merge window so the next branches should be empty), everyone CCed on this mail is listed as a contact for each tree - please let me know if that needs an update.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.