All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue
Date: Thu, 18 May 2017 15:58:50 +0200	[thread overview]
Message-ID: <20170518135850.GA24513@kroah.com> (raw)
In-Reply-To: <1495104615-4752-1-git-send-email-srishtishar@gmail.com>

On Thu, May 18, 2017 at 04:20:15PM +0530, srishti wrote:
> From: srishti sharma <srishtishar@gmail.com>
> 
> Fixed a trailing */ issue.
> 
> Signed-off-by: srishti sharma <srishtishar@gmail.com>
> ---
>  drivers/staging/bcm2835-audio/bcm2835-ctl.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

You sent two copies of this, which am I supposed to apply?  And what
changed from the last version?

I'm dropping this, please fix and only send _one_ copy of the patch.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: srishti <srishtishar@gmail.com>
Cc: devel@driverdev.osuosl.org, f.fainelli@gmail.com,
	sbranden@broadcom.com, swarren@wwwdotorg.org, rjui@broadcom.com,
	lee@kernel.org, vicmos89@gmail.com, linux-kernel@vger.kernel.org,
	eric@anholt.net, bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org, mzoran@crowfest.net,
	dan.carpenter@oracle.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue
Date: Thu, 18 May 2017 15:58:50 +0200	[thread overview]
Message-ID: <20170518135850.GA24513@kroah.com> (raw)
In-Reply-To: <1495104615-4752-1-git-send-email-srishtishar@gmail.com>

On Thu, May 18, 2017 at 04:20:15PM +0530, srishti wrote:
> From: srishti sharma <srishtishar@gmail.com>
> 
> Fixed a trailing */ issue.
> 
> Signed-off-by: srishti sharma <srishtishar@gmail.com>
> ---
>  drivers/staging/bcm2835-audio/bcm2835-ctl.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

You sent two copies of this, which am I supposed to apply?  And what
changed from the last version?

I'm dropping this, please fix and only send _one_ copy of the patch.

thanks,

greg k-h

  reply	other threads:[~2017-05-18 13:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 10:50 [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue srishti
2017-05-18 10:50 ` srishti
2017-05-18 13:58 ` Greg KH [this message]
2017-05-18 13:58   ` Greg KH
     [not found]   ` <CAB3L5owb2go2Hik5iMRuzXzOdfyKH+gM27_ugfady79bXSnHuQ@mail.gmail.com>
2017-05-18 15:40     ` Fwd: " srishti sharma
2017-05-18 15:40       ` srishti sharma
2017-05-19 19:30   ` srishti sharma
2017-05-19 19:30     ` srishti sharma
2017-05-19 19:33     ` Dan Carpenter
2017-05-19 19:33       ` Dan Carpenter
2017-05-19 19:56       ` srishti sharma
2017-05-19 19:56         ` srishti sharma
  -- strict thread matches above, loose matches on Subject: below --
2017-05-19 20:30 srishti sharma
2017-05-19 20:30 ` srishti sharma
2017-05-25 16:57 ` Greg KH
2017-05-25 16:57   ` Greg KH
2017-05-25 19:27   ` srishti sharma
2017-05-25 19:27     ` srishti sharma
2017-05-18 10:42 srishti
2017-05-18 10:42 ` srishti
2017-05-18 10:07 srishti
2017-05-18 10:07 ` srishti
2017-05-18 10:13 ` Dan Carpenter
2017-05-18 10:13   ` Dan Carpenter

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=20170518135850.GA24513@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.