On Tue, 21 Aug 2012 10:23:54 -0400 Alexandre Bounine <alexandre.boun...@idt.com> wrote:
> Modify mport device name assignment to provide clear reference to devices > in systems with multiple Tsi721 bridges. > > This patch is applicable to kernel versions starting from v3.2. This seems to imply that you think the patch should be backported into earlier kernels. But no reason for doing this was provided. > --- a/drivers/rapidio/devices/tsi721.c > +++ b/drivers/rapidio/devices/tsi721.c > @@ -2165,7 +2165,8 @@ static int __devinit tsi721_setup_mport(struct > tsi721_device *priv) > rio_init_dbell_res(&mport->riores[RIO_DOORBELL_RESOURCE], 0, 0xffff); > rio_init_mbox_res(&mport->riores[RIO_INB_MBOX_RESOURCE], 0, 3); > rio_init_mbox_res(&mport->riores[RIO_OUTB_MBOX_RESOURCE], 0, 3); > - strcpy(mport->name, "Tsi721 mport"); > + snprintf(mport->name, RIO_MAX_MPORT_NAME, "%s(%s)", > + dev_driver_string(&pdev->dev), dev_name(&pdev->dev)); And it's a non-back-compatible change to a userspace-visible interface! As such we'd need extraordinary justification to merge it into *future* kernels, let alone backport it. Please, do provide much better changelogging than this. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
