From: Greg KH <gregkh@linuxfoundation.org>
To: srishti sharma <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, 25 May 2017 18:57:07 +0200 [thread overview]
Message-ID: <20170525165706.GA1201@kroah.com> (raw)
In-Reply-To: <1495225824-4422-1-git-send-email-srishtishar@gmail.com>
On Sat, May 20, 2017 at 02:00:24AM +0530, srishti sharma wrote:
> 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(-)
This file isn't in my tree, always work against linux-next please...
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-25 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 20:30 [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue srishti sharma
2017-05-25 16:57 ` Greg KH [this message]
2017-05-25 19:27 ` srishti sharma
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 10:50 srishti
2017-05-18 13:58 ` Greg KH
2017-05-19 19:30 ` srishti sharma
2017-05-19 19:33 ` Dan Carpenter
2017-05-19 19:56 ` srishti sharma
2017-05-18 10:42 srishti
2017-05-18 10:07 srishti
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=20170525165706.GA1201@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.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=mzoran@crowfest.net \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=srishtishar@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=vicmos89@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox