All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Deepak Mishra <linux.dkm@gmail.com>
Cc: linux-kernel@vger.kernel.org, Larry.Finger@lwfinger.net,
	florian.c.schilhabel@googlemail.com, himadri18.07@gmail.com,
	straube.linux@gmail.com
Subject: Re: [PATCH 0/8] staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
Date: Sun, 2 Jun 2019 08:20:47 +0200	[thread overview]
Message-ID: <20190602062047.GA12076@kroah.com> (raw)
In-Reply-To: <cover.1559412149.git.linux.dkm@gmail.com>

On Sun, Jun 02, 2019 at 12:13:34AM +0530, Deepak Mishra wrote:
> This patchset fixes CamelCase checks in struct _adapter in drv_types.h
> and in files where struct _adapter is used by renaming the variables
> without camel case. 
> 
> These check were reported by checkpatch.pl
>   
> Deepak Mishra (8):
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
>   staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h

All of these patches had the same subject line, yet did diffferent
things, that's not ok :(

Please fix this series up to have unique subject lines and resend.

thanks,

greg k-h

      parent reply	other threads:[~2019-06-02  6:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-01 18:43 [PATCH 0/8] staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h Deepak Mishra
2019-06-01 18:43 ` [PATCH 1/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 2/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 3/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 4/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 5/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 6/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 7/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 8/8] " Deepak Mishra
2019-06-01 19:26   ` Joe Perches
2019-06-02 10:12     ` Deepak Mishra
2019-06-02  6:20 ` Greg KH [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=20190602062047.GA12076@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=himadri18.07@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.dkm@gmail.com \
    --cc=straube.linux@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.