From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Ofir Drang <ofir.drang@arm.com>
Subject: Re: [PATCH 0/4] staging: ccree: coding style clean ups
Date: Thu, 27 Jul 2017 21:55:09 -0700 [thread overview]
Message-ID: <20170728045509.GA24659@kroah.com> (raw)
In-Reply-To: <1501152199-7671-1-git-send-email-gilad@benyossef.com>
On Thu, Jul 27, 2017 at 01:43:14PM +0300, Gilad Ben-Yossef wrote:
> Misc. coding style fixes for ccree driver.
>
> These are the missing patches that failed to apply two weeks ago,
> rebased onto latest staging-next.
>
> By the way, I still do not understand why they failed to apply,
> as they applied just fine being cherry picked on top of latest
> staging-next apart for fixes for later changes. I hope these will
> be good.
Only one applied here :(
I did just take some more coding style fixes from someone else who sent
them before you did as they looked correct, maybe that's why? Can you
rebase and resend?
thanks,
greg k-h
prev parent reply other threads:[~2017-07-28 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 10:43 [PATCH 0/4] staging: ccree: coding style clean ups Gilad Ben-Yossef
2017-07-27 10:43 ` [PATCH 1/4] staging: ccree: fix parenthesis alignment Gilad Ben-Yossef
2017-07-27 10:43 ` [PATCH 2/4] staging: ccree: fix split strings Gilad Ben-Yossef
2017-07-27 10:43 ` [PATCH 3/4] staging: ccree: remove func name from log messages Gilad Ben-Yossef
2017-07-27 10:43 ` [PATCH 4/4] staging: ccree: kmalloc by sizeof var not type Gilad Ben-Yossef
2017-07-28 4:55 ` Greg Kroah-Hartman [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=20170728045509.GA24659@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gilad@benyossef.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ofir.drang@arm.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;
as well as URLs for NNTP newsgroup(s).