All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: "Hatice ERTÜRK" <haticeerturk27@gmail.com>,
	outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 11/11] Staging: drivers: usb: serial: ipw: Deleted space
Date: Fri, 20 Feb 2015 12:04:09 -0500	[thread overview]
Message-ID: <54E76909.5080705@gmail.com> (raw)
In-Reply-To: <1424451380-4051-1-git-send-email-haticeerturk27@gmail.com>

On 02/20/15 11:56, Hatice ERTÜRK wrote:
> Deleted spaces in 263 line.
> Used the checkpatch.pl.
> 
> Signed-off-by: Hatice ERTURK <haticeerturk27@gmail.com>
> ---
>  drivers/usb/serial/ipw.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

It would be better to describe this as 'Deleted spaces mixed into tab
indentation'.

In addition, when you post a set of patches, you should post them as one
set, rather than individual emails. Using a cover letter for the whole
set is recommended.

Cheers,
Jes


> diff --git a/drivers/usb/serial/ipw.c b/drivers/usb/serial/ipw.c
> index 8b1cf18..150bca9 100644
> --- a/drivers/usb/serial/ipw.c
> +++ b/drivers/usb/serial/ipw.c
> @@ -260,7 +260,7 @@ static void ipw_close(struct usb_serial_port *port)
>  	dev_dbg(dev, "%s:sending purge\n", __func__);
>  	result = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
>  			 IPW_SIO_PURGE, USB_TYPE_VENDOR |
> -			 		USB_RECIP_INTERFACE | USB_DIR_OUT,
> +					USB_RECIP_INTERFACE | USB_DIR_OUT,
>  			 0x03,
>  			 0,
>  			 NULL,
> 



       reply	other threads:[~2015-02-20 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1424451380-4051-1-git-send-email-haticeerturk27@gmail.com>
2015-02-20 17:04 ` Jes Sorensen [this message]
2015-02-20 17:04 ` [Outreachy kernel] [PATCH 11/11] Staging: drivers: usb: serial: ipw: Deleted space Julia Lawall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54E76909.5080705@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=haticeerturk27@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.