Hi David. Small nitpick.. > diff --git a/drivers/char/hw_random/Makefile b/drivers/char/hw_random/Makefile > index c8b7300..32b327b 100644 > --- a/drivers/char/hw_random/Makefile > +++ b/drivers/char/hw_random/Makefile > @@ -7,6 +7,8 @@ rng-core-y := core.o > obj-$(CONFIG_HW_RANDOM_INTEL) += intel-rng.o > obj-$(CONFIG_HW_RANDOM_AMD) += amd-rng.o > obj-$(CONFIG_HW_RANDOM_GEODE) += geode-rng.o > +obj-$(CONFIG_HW_RANDOM_N2RNG) += n2-rng.o > +n2-rng-objs := n2-drv.o n2-asm.o These days the preferred syntax is: n2-rng-y := n2-drv.o n2-asm.o Following this scheme in general allows us to easily introduce: n2-rng-$(CONFIG_FOO) += foo.o I do not assume your n2-rng will need this, but doing so in general is a win. > obj-$(CONFIG_HW_RANDOM_VIA) += via-rng.o > obj-$(CONFIG_HW_RANDOM_IXP4XX) += ixp4xx-rng.o > obj-$(CONFIG_HW_RANDOM_OMAP) += omap-rng.o > diff --git a/drivers/char/hw_random/n2-asm.S b/drivers/char/hw_random/n2-asm.S > new file mode 100644 > index 0000000..c504e53 > --- /dev/null > +++ b/drivers/char/hw_random/n2-asm.S > @@ -0,0 +1,93 @@ > +/* n2-asm.S: Niagara2 RNG hypervisor call assembler. > + * > + * Copyright (C) 2008 David S. Miller <davem@xxxxxxxxxxxxx> > + */ > +#include <asm/hypervisor.h> > +#include "n2rng.h" > + > + .text I had expected: .section .text, "aw" here?? (Maybe init.h should define a __TEXT macro).. > + .globl sun4v_rng_get_diag_ctl > + .type sun4v_rng_get_diag_ctl,#function > +sun4v_rng_get_diag_ctl: > + mov HV_FAST_RNG_GET_DIAG_CTL, %o5 > + ta HV_FAST_TRAP > + retl > + nop > + .size sun4v_rng_get_diag_ctl,.-sun4v_rng_get_diag_ctl Any specific reason why you do not use: ENTRY(sun4v_rng_get_diag_ctl) mov HV_FAST_RNG_GET_DIAG_CTL, %o5 ta HV_FAST_TRAP retl nop ENDPROC(sun4v_rng_get_diag_ctl) I see these uses in other places and it do the .globl, .type, .size and the label: stuff for you. This is a general comment for all the 'functions' in this file. Only browsed the rest - looked good. Sam -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html