From: Dhiru Kholia <dhiru.kholia@gmail.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1] staging: ccree: fix all whitespace errors
Date: Thu, 18 May 2017 11:29:30 +0530 [thread overview]
Message-ID: <20170518055930.znzlu45xfjrbbw54@lonestar> (raw)
In-Reply-To: <CAOtvUMduAYmhSDZ=Gcmuvo2NsaN-XguL53ae=1xOZ_djVB3Z-g@mail.gmail.com>
On Sun, May 14, 2017 at 08:53:02AM +0300, Gilad Ben-Yossef wrote:
> Hi Dhiru,
>
> On Sat, May 13, 2017 at 5:52 PM, Dhiru Kholia <dhiru.kholia@gmail.com> wrote:
> > These whitespace issues were found by the checkpatch.pl script. This
> > patch helps in making the staging tree a bit cleaner.
> >
> > Signed-off-by: Dhiru Kholia <dhiru.kholia@gmail.com>
> > ---
> > drivers/staging/ccree/TODO | 2 +-
> > drivers/staging/ccree/cc_bitops.h | 6 +-
> > drivers/staging/ccree/cc_crypto_ctx.h | 8 +--
> > drivers/staging/ccree/cc_hal.h | 6 +-
> > drivers/staging/ccree/cc_hw_queue_defs.h | 116 +++++++++++++++---------------
> > drivers/staging/ccree/cc_lli_defs.h | 6 +-
> > drivers/staging/ccree/cc_pal_log.h | 12 ++--
> > drivers/staging/ccree/cc_pal_log_plat.h | 6 +-
> > drivers/staging/ccree/cc_pal_types.h | 42 +++++------
> > drivers/staging/ccree/cc_pal_types_plat.h | 8 +--
> > drivers/staging/ccree/cc_regs.h | 10 +--
> > 11 files changed, 111 insertions(+), 111 deletions(-)
>
> I'm sorry, but your patch doesn't apply after the recent patch set that
> removed some of those files.
True.
The good news is that my patch is no longer needed. The current ccree
code in linux-next seems to be free of any whitespace issues.
Thanks,
Dhiru
next prev parent reply other threads:[~2017-05-18 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 14:52 [PATCH v1] staging: ccree: fix all whitespace errors Dhiru Kholia
2017-05-14 5:53 ` Gilad Ben-Yossef
2017-05-18 5:59 ` Dhiru Kholia [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-10 15:44 Dhiru Kholia
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=20170518055930.znzlu45xfjrbbw54@lonestar \
--to=dhiru.kholia@gmail.com \
--cc=gilad@benyossef.com \
--cc=gregkh@linuxfoundation.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).