From: Greg KH <gregkh@linuxfoundation.org>
To: srishti sharma <srishtishar@gmail.com>
Cc: stefan.wahren@i2se.com, eric@anholt.net, lee@kernel.org,
f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: vc04_services: bcm2835-audio: bcm2835-ctl.c: Fixed alignment to match open parenthesis
Date: Sat, 24 Jun 2017 00:20:55 +0800 [thread overview]
Message-ID: <20170623162055.GB21608@kroah.com> (raw)
In-Reply-To: <1497468895-3061-1-git-send-email-srishtishar@gmail.com>
On Thu, Jun 15, 2017 at 01:04:55AM +0530, srishti sharma wrote:
> Fixed alignment so that it matched open parenthesis.
>
> Signed-off-by: srishti sharma <srishtishar@gmail.com>
> ---
> .../staging/vc04_services/bcm2835-audio/bcm2835-ctl.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
What differs from your previous patch? Always properly version your
patch so we know what to take.
Please fix and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-23 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 19:34 [PATCH] Staging: vc04_services: bcm2835-audio: bcm2835-ctl.c: Fixed alignment to match open parenthesis srishti sharma
2017-06-23 16:20 ` Greg KH [this message]
2017-06-24 2:41 ` srishti sharma
2017-06-24 3:30 ` srishti sharma
-- strict thread matches above, loose matches on Subject: below --
2017-06-09 21:07 srishti sharma
2017-06-13 13:00 ` Greg KH
2017-06-13 14:37 ` srishti sharma
2017-06-13 14:47 ` Dan Carpenter
2017-06-13 21:45 ` srishti sharma
2017-06-14 5:09 ` Greg KH
2017-06-14 13:41 ` srishti sharma
2017-06-14 13:49 ` Greg KH
2017-06-14 13:52 ` srishti sharma
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=20170623162055.GB21608@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=srishtishar@gmail.com \
--cc=stefan.wahren@i2se.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox