[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <934e298f-596d-dc13-f3e3-797a49c74e84@users.sourceforge.net>
Date: Sat, 26 Aug 2017 09:00:43 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Martyn Welch <martyn@...chs.me.uk>, devel@...verdev.osuosl.org
Cc: Aaron Sierra <asierra@...-inc.com>,
Alessio Igor Bogani <alessio.bogani@...ttra.eu>,
Arnd Bergmann <arnd@...db.de>,
Augusto Mecking Caringi <augustocaringi@...il.com>,
Baoyou Xie <baoyou.xie@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Manohar Vanga <manohar.vanga@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 13/14] vme: tsi148: Improve 17 size determinations
>> @@ -2363,5 +2364,5 @@ static int tsi148_probe(struct pci_dev *pdev, const struct pci_device_id *id)
>> master_num--;
>>
>> tsi148_device->flush_image =
>> - kmalloc(sizeof(struct vme_master_resource), GFP_KERNEL);
>> + kmalloc(sizeof(*tsi148_device->flush_image), GFP_KERNEL);
>
> This line is now a tiny bit too long
Can you eventually tolerate a line length of 81 characters at such a source code place?
> and needs to be broken over two lines.
How would like to achieve this?
* It seems that you would not like to perform such a tweak yourself.
* Do you expect a resend for the complete patch series?
* Will it be sufficient to send another patch only for the requested reformatting
of a single line?
Regards,
Markus
Powered by blists - more mailing lists