On 26 August 2017 at 08:00, SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx> wrote: >>> @@ -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? > I think there's some irony here. On the one hand you are submitting patches that correct coding style issues, on the other you are asking whether we can ignore the coding style... > >> 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. > To be honest, it is quicker and easier in this instance to do just that. So that's now done. Patches now in my testing branch: https://gitlab.collabora.com/martyn/linux/commits/vme-testing For future reference: > * Do you expect a resend for the complete patch series? > Unless the maintainer has commented that they have accepted patches x, y and z, then sending the entire series again is generally the right thing to do. > * Will it be sufficient to send another patch only for the requested reformatting > of a single line? > No, unless the patches have been accepted as-is. Martyn -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
