From: Julia Lawall <julia.lawall@lip6.fr>
To: Ioannis Valasakis <code@wizofe.uk>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [PATCH] staging: greybus: remove extra space before tab
Date: Sat, 3 Nov 2018 07:57:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1811030757170.2922@hadrien> (raw)
In-Reply-To: <20181102234508.GA27353@kvasir.local>
On Fri, 2 Nov 2018, Ioannis Valasakis wrote:
> Remove extra spaces before the tab character inside a comment section.
> Reported by checkpatch.
>
> Signed-off-by: Ioannis Valasakis <code@wizofe.uk>
> ---
> drivers/staging/greybus/greybus_protocols.h | 4 ++--
You seem to have sent three patches on this file. Greg will want them to
be in a series, to reduce ambiguity about how they should be applied.
Likewise for the other files.
julia
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/greybus_protocols.h b/drivers/staging/greybus/greybus_protocols.h
> index 5783f715bdc2..429a952c5200 100644
> --- a/drivers/staging/greybus/greybus_protocols.h
> +++ b/drivers/staging/greybus/greybus_protocols.h
> @@ -918,8 +918,8 @@ struct gb_spi_device_config_response {
> * 0 the default (from @spi_device) is used.
> * @len: size of rx and tx buffers (in bytes)
> * @delay_usecs: microseconds to delay after this transfer before (optionally)
> - * changing the chipselect status, then starting the next transfer or
> - * completing this spi_message.
> + * changing the chipselect status, then starting the next transfer or
> + * completing this spi_message.
> * @cs_change: affects chipselect after this transfer completes
> * @bits_per_word: select a bits_per_word other than the device default for this
> * transfer. If 0 the default (from @spi_device) is used.
> --
> 2.19.1
>
>
> --
> ta
> ioannis
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20181102234508.GA27353%40kvasir.local.
> For more options, visit https://groups.google.com/d/optout.
>
next prev parent reply other threads:[~2018-11-03 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 23:45 [PATCH] staging: greybus: remove extra space before tab Ioannis Valasakis
2018-11-03 6:57 ` Julia Lawall [this message]
2018-11-03 11:37 ` [Outreachy kernel] " tungolcild
2018-11-03 14:18 ` 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=alpine.DEB.2.21.1811030757170.2922@hadrien \
--to=julia.lawall@lip6.fr \
--cc=code@wizofe.uk \
--cc=gregkh@linuxfoundation.org \
--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.