From: srishti sharma <srishtishar@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/4] Staging: ccree: cc_crypto_ctx.h: Added * on subsequent lines of a comment block.
Date: Tue, 6 Jun 2017 19:10:48 +0530 [thread overview]
Message-ID: <CAB3L5oxeQjSAJwsS1d9FuZtf_P6noosAFSfkK016PY118WgwPg@mail.gmail.com> (raw)
In-Reply-To: <20170604081957.GA28749@kroah.com>
On Sun, Jun 4, 2017 at 1:49 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Sun, Jun 04, 2017 at 05:02:08AM +0530, srishti sharma wrote:
>> Added * on subsequent lines of a comment block.
>>
>> Signed-off-by: srishti sharma <srishtishar@gmail.com>
>> ---
>> drivers/staging/ccree/cc_crypto_ctx.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> This whole series also does not apply. Note, this driver is under
> active development, you are probably running into the problem that lots
> of people are working on it at the same time.
>
> sorry,
>
> greg k-h
Okay , Thanks a lot !
Regards,
Srishti
next prev parent reply other threads:[~2017-06-06 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 23:31 [PATCH 0/4] Fixed comment coding style issues srishti sharma
2017-06-03 23:32 ` [PATCH 1/4] Staging: ccree: cc_crypto_ctx.h: Added * on subsequent lines of a comment block srishti sharma
2017-06-04 8:19 ` Greg KH
2017-06-06 13:40 ` srishti sharma [this message]
2017-06-03 23:32 ` [PATCH 2/4] Staging: ccree: cc_crypto_ctx.h: Fixed trailing */ issue in " srishti sharma
2017-06-03 23:33 ` [PATCH 3/4] Staging: ccree: cc_crypto_ctx.h: Fixed * alignment issues " srishti sharma
2017-06-03 23:33 ` [PATCH 4/4] Staging: ccree: cc_crypto_ctx.h: Added * on subsequent lines of " 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=CAB3L5oxeQjSAJwsS1d9FuZtf_P6noosAFSfkK016PY118WgwPg@mail.gmail.com \
--to=srishtishar@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).