Skip to contentSkip to conversation

git tree for y2038 patches, to be added to linux-next

DISCUSSION Arnd Bergmann 2 participants 2 messages Oct 23, 2014 – Oct 26, 2014

lore
Share & tools
lore
#0 lore raw

Hi Stephen,

I'm collecting patches for 64-bit time_t conversion. I'm getting patches for this topic from the OPW application, and hopefully soon from an intern in the program.

The plan is to have most of the patches being merged through subsystem maintainer trees as much as possible, but I also want to give them linux-next exposure as early as possible, in particular since a lot of the code that is being changed is not actively maintained. I will send the remaining patches to Thomas Gleixner so he can put them into the tip tree.

Please add

git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git y2038

to linux-next. At the moment there is only one simple patch in it, I assume there will be more soon.

Arnd

#1 lore raw

Hi Arnd,

Quoted 11 lines · On Thu, 23 Oct 2014 22:15:24 +0200 Arnd Bergmann <[email protected]> wrote:

I'm collecting patches for 64-bit time_t conversion. I'm getting patches for this topic from the OPW application, and hopefully soon from an intern in the program.

The plan is to have most of the patches being merged through subsystem maintainer trees as much as possible, but I also want to give them linux-next exposure as early as possible, in particular since a lot of the code that is being changed is not actively maintained. I will send the remaining patches to Thomas Gleixner so he can put them into the tip tree.

Quoted 6 lines

Please add

git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git y2038

to linux-next. At the moment there is only one simple patch in it, I assume there will be more soon.

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment 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.

Signature · 3 lines
Cheers,
Stephen Rothwell 
[email protected]