lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 26 Aug 2017 09:00:43 +0200
From:   SF Markus Elfring <>
To:     Martyn Welch <>,
Cc:     Aaron Sierra <>,
        Alessio Igor Bogani <>,
        Arnd Bergmann <>,
        Augusto Mecking Caringi <>,
        Baoyou Xie <>,
        Greg Kroah-Hartman <>,
        Manohar Vanga <>,
        LKML <>,
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?


Powered by blists - more mailing lists