All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: "Forest Bond" <forest@alittletooquiet.net>,
	"Madhumitha Prabakaran" <madhumithabiw@gmail.com>,
	"Lucas Henneman" <lucas.henneman@linaro.org>,
	"Yujia Qiao" <rapiz@foxmail.com>,
	"Marcos Antonio de Jesus Filho" <mdejesusfilho@gmail.com>,
	"Edmundo Carmona Antoranz" <eantoranz@gmail.com>,
	"Aldas Taraškevičius" <aldas60@gmail.com>,
	"Deepak R Varma" <mh12gx2825@gmail.com>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: fix camelcase in byLocalID
Date: Sun, 10 Oct 2021 14:53:13 +0200	[thread overview]
Message-ID: <YWLiOUbdBEJcq2u3@kroah.com> (raw)
In-Reply-To: <20211008174512.36617-1-tomm.merciai@gmail.com>

On Fri, Oct 08, 2021 at 07:44:57PM +0200, Tommaso Merciai wrote:
> Replace camel case variable name for variable byLocalID
> with snake case equivalent.
> 
> Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> ---
>  drivers/staging/vt6655/baseband.c    | 2 +-
>  drivers/staging/vt6655/card.c        | 2 +-
>  drivers/staging/vt6655/channel.c     | 2 +-
>  drivers/staging/vt6655/device.h      | 2 +-
>  drivers/staging/vt6655/device_main.c | 6 +++---
>  drivers/staging/vt6655/dpc.c         | 2 +-
>  drivers/staging/vt6655/key.c         | 2 +-
>  drivers/staging/vt6655/mac.c         | 4 ++--
>  drivers/staging/vt6655/mac.h         | 2 +-
>  drivers/staging/vt6655/rxtx.c        | 2 +-
>  10 files changed, 13 insertions(+), 13 deletions(-)

Does not apply on top of your other patch series :(

Can you rebase and resend?

thanks,

greg k-h

      reply	other threads:[~2021-10-10 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 17:44 [PATCH] staging: vt6655: fix camelcase in byLocalID Tommaso Merciai
2021-10-08 17:44 ` Tommaso Merciai
2021-10-10 12:53 ` Greg Kroah-Hartman [this message]

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=YWLiOUbdBEJcq2u3@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aldas60@gmail.com \
    --cc=eantoranz@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gustavoars@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=lucas.henneman@linaro.org \
    --cc=madhumithabiw@gmail.com \
    --cc=mdejesusfilho@gmail.com \
    --cc=mh12gx2825@gmail.com \
    --cc=rapiz@foxmail.com \
    --cc=tomm.merciai@gmail.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.