All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: "Forest Bond" <forest@alittletooquiet.net>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Madhumitha Prabakaran" <madhumithabiw@gmail.com>,
	"Yujia Qiao" <rapiz@foxmail.com>,
	"Lucas Henneman" <lucas.henneman@linaro.org>,
	"Aldas Taraškevičius" <aldas60@gmail.com>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	"Deepak R Varma" <mh12gx2825@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: Replace camel case variable name
Date: Thu, 23 Sep 2021 11:30:19 +0300	[thread overview]
Message-ID: <20210923083018.GB2048@kadam> (raw)
In-Reply-To: <20210922225756.694409-1-tomm.merciai@gmail.com>

You sent about 10 patches with exact same subject.

On Thu, Sep 23, 2021 at 12:57:52AM +0200, Tommaso Merciai wrote:
> Work in progress: replace camel case variables

Leave out the "work in progress".  We're only interested in what this
specific patch, not other patches.

regards,
dan carpenter


  reply	other threads:[~2021-09-23  8:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 22:57 [PATCH] staging: vt6655: Replace camel case variable name Tommaso Merciai
2021-09-22 22:57 ` Tommaso Merciai
2021-09-23  8:30 ` Dan Carpenter [this message]
2021-09-24 21:11   ` Tommaso Merciai
  -- strict thread matches above, loose matches on Subject: below --
2021-09-22 22:51 Tommaso Merciai
2021-09-22 22:51 ` Tommaso Merciai
2021-09-22 23:12 ` Gustavo A. R. Silva
2021-09-24 21:09   ` Tommaso Merciai
2021-09-22 22:35 Tommaso Merciai
2021-09-22 22:35 ` Tommaso Merciai
2021-09-22 22:29 Tommaso Merciai
2021-09-22 22:29 ` Tommaso Merciai
2021-09-22 22:13 Tommaso Merciai
2021-09-22 22:13 ` Tommaso Merciai
2021-09-22 22:07 [PATCH] Staging: " Tommaso Merciai
2021-09-22 22:07 ` Tommaso Merciai
2021-09-23 19:54 ` Fabio M. De Francesco
2021-09-24 21:12   ` Tommaso Merciai

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=20210923083018.GB2048@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=aldas60@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --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=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.