[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170629141829.GA29662@kroah.com>
Date: Thu, 29 Jun 2017 16:18:29 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: karthik <karthik@...hveda.org>
Cc: Gilad Ben-Yossef <gilad@...yossef.com>, devel@...verdev.osuosl.org,
driverdev-devel@...uxdriverproject.org,
Linux kernel mailing list <linux-kernel@...r.kernel.org>,
linux-crypto@...r.kernel.org, sunil.m@...hveda.org
Subject: Re: [PATCH 0/2] staging: ccree: Fix coding style and remove warnings
On Thu, Jun 29, 2017 at 04:13:38PM +0530, karthik wrote:
> On Wednesday 28 June 2017 03:15 PM, Gilad Ben-Yossef wrote:
> > Thank you Karthik,
> >
> > On Wed, Jun 28, 2017 at 12:37 PM, <karthik@...hveda.org> wrote:
> > > From: Karthik Tummala <karthik@...hveda.org>
> > >
> > > This patch series fixes coding style and removes the following
> > > checkpatch.pl warnings:
> > >
> > > Prefer using '"%s...", __func__' to using the function's name,
> > > in a string.
> >
> > This one is good.
> > >
> > > Braces {} are not necessary for single statement blocks.
> >
> > I have already sent a patch addressing this and some other things
> > yesterday/
> >
> > >
> > > Rebased on top of next-20170627.
> > > Patches were tested and built on next-20170627
> >
> > Can you please check patch 1 still applies after yesterdays patch series?
> Hi, I have applied your patch series and then tried to apply patch 1 and it
> failed. Should I wait until the patch series gets accepted and then continue
> my work on the new linux-next release ? or is there any other option ?
You need to rebased on top of these changes. All of them are now in
staging-testing, soon to move to staging-next in a day or so. Rebase on
there and resend.
thanks,
greg k-h
Powered by blists - more mailing lists