Skip to contentSkip to conversation

ksignal changes for 3.9

DISCUSSION Vineet Gupta 2 participants 2 messages Feb 13, 2013 – Feb 14, 2013 Generic include/asm header files

lore
Share & tools
lore
#0 lore raw

Hi Al,

linux-next contains ksignal conversion for some of the architectures. Are you planning to complete that in 3.9 merge window. The reason I ask is so that the newer architectures (arc/metag - for a likely 3.9 merge) can queue the corresponding changes via respective trees.

Thx,
-Vineet

#1 lore raw
Quoted 6 lines · Vineet Gupta

Hi Al,

linux-next contains ksignal conversion for some of the architectures. Are you planning to complete that in 3.9 merge window. The reason I ask is so that the newer architectures (arc/metag - for a likely 3.9 merge) can queue the corresponding changes via respective trees.

That's hardly urgent; as far as I'm concerned, ksignal conversion is for 3.10-rc1. OTOH, these helpers are for 3.9-rc1, so any architecture that cares to switch is welcome to it; less work for me that way. Hell, as far as I'm concerned, any maintainer of an in-tree architecture who's happy with arch-$ARCHITECTURE is welcome to say so and pull it into their tree right now. That'll bring the stem of signal.git in, complete with ksignal helpers to play with. That part is in no-rebase mode. The same goes for arc and metag, except that you'd need to pull the branchpoint of arch-* (signal.git#Base) instead...