Messages in this thread | | | Date | Tue, 5 Jul 2022 08:25:16 +0200 | From | Greg KH <> | Subject | Re: [PATCH] char: lp: Fix spelling mistake and add spaces |
| |
On Tue, Jul 05, 2022 at 02:15:18PM +0800, Zhang Jiaming wrote: > Fix spelling of doesn' t. > Add spaces around '=' and ','. > > Signed-off-by: Zhang Jiaming <jiaming@nfschina.com> > --- > drivers/char/lp.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/char/lp.c b/drivers/char/lp.c > index 38aad99ebb61..214fb037fa76 100644 > --- a/drivers/char/lp.c > +++ b/drivers/char/lp.c > @@ -26,7 +26,7 @@ > * be still BUSY. This is needed at least with Epson Stylus Color. To enable > * the new TRUST_IRQ mode read the `LP OPTIMIZATION' section below... > * Fixed the irq on the rising edge of the strobe case. > - * Obsoleted the CAREFUL flag since a printer that doesn' t work with > + * Obsoleted the CAREFUL flag since a printer that doesn't work with > * CAREFUL will block a bit after in lp_check_status(). > * Andrea Arcangeli, 15 Oct 1998 > * Obsoleted and removed all the lowlevel stuff implemented in the last > @@ -418,7 +418,7 @@ static ssize_t lp_read(struct file *file, char __user *buf, > size_t count, loff_t *ppos) > { > DEFINE_WAIT(wait); > - unsigned int minor=iminor(file_inode(file)); > + unsigned int minor = iminor(file_inode(file)); > struct parport *port = lp_table[minor].dev->port; > ssize_t retval = 0; > char *kbuf = lp_table[minor].lp_buffer; > @@ -965,7 +965,7 @@ static void lp_attach(struct parport *port) > port->probe_info[0].class != PARPORT_CLASS_PRINTER) > return; > if (lp_count == LP_NO) { > - printk(KERN_INFO "lp: ignoring parallel port (max. %d)\n",LP_NO); > + printk(KERN_INFO "lp: ignoring parallel port (max. %d)\n", LP_NO); > return; > } > for (i = 0; i < LP_NO; i++) > -- > 2.34.1 >
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- Your patch did many different things all at once, making it difficult to review. All Linux kernel patches need to only do one thing at a time. If you need to do multiple things (such as clean up all coding style issues in a file/driver), do it in a sequence of patches, each one doing only one thing. This will make it easier to review the patches to ensure that they are correct, and to help alleviate any merge issues that larger patches can cause.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot
| |