From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Namrata A Shettar <namrataashettar@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
Rithvik Patibandla <rithvikp98@gmail.com>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH v2] staging: vt6656: Remove unnecessary return values
Date: Thu, 29 Sep 2016 08:21:09 +0200 [thread overview]
Message-ID: <20160929062109.GB28764@kroah.com> (raw)
In-Reply-To: <20160928172756.GA4337@namrata-HP-Pavilion-g6-Notebook-PC>
On Wed, Sep 28, 2016 at 10:57:58PM +0530, Namrata A Shettar wrote:
> On Wed, Sep 28, 2016 at 11:36:06AM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Sep 27, 2016 at 11:48:47PM +0530, Namrata A Shettar wrote:
> > > Remove unnecessary return values. Change return type of corresponding
> > > functions to 'void' and comments.
> > >
> > > Signed-off-by: Namrata A Shettar <namrataashettar@gmail.com>
> > > ---
> > > Changes in v2:
> > > - combine both patches of prior patchset
> > >
> > > drivers/staging/vt6656/card.c | 22 ++++++----------------
> > > drivers/staging/vt6656/card.h | 6 +++---
> > > 2 files changed, 9 insertions(+), 19 deletions(-)
> >
> > Doesn't apply to my tree at all :(
>
> Is there a work-around for this? or anything I could have possibly gone
> wrong with?
I don't remember, try rebasing to see what the conflicts are, or perhaps
someone else already sent in this same type of change? We are averaging
about 20-30 patches added to the staging tree each day right now,
sometimes people end up doing the same work at the same time, sorry.
greg k-h
next prev parent reply other threads:[~2016-09-29 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 18:18 [PATCH v2] staging: vt6656: Remove unnecessary return values Namrata A Shettar
2016-09-28 9:36 ` Greg Kroah-Hartman
2016-09-28 17:27 ` Namrata A Shettar
2016-09-29 6:21 ` Greg Kroah-Hartman [this message]
2016-09-29 17:17 ` Namrata A Shettar
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=20160929062109.GB28764@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=namrataashettar@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=rithvikp98@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.