From: Oscar Carter <oscar.carter@gmx.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Oscar Carter <oscar.carter@gmx.com>,
Forest Bond <forest@alittletooquiet.net>,
devel@driverdev.osuosl.org,
Malcolm Priestley <tvboxspy@gmail.com>,
"John B. Wyatt IV" <jbwyatt4@gmail.com>,
linux-kernel@vger.kernel.org, Stefano Brivio <sbrivio@redhat.com>,
Colin Ian King <colin.king@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v3 0/2] staging: vt6656: Check the return value of vnt_control_out_* calls
Date: Sat, 25 Apr 2020 15:33:45 +0200 [thread overview]
Message-ID: <20200425133345.GA3213@ubuntu> (raw)
In-Reply-To: <20200425105626.GA2071483@kroah.com>
On Sat, Apr 25, 2020 at 12:56:26PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Apr 23, 2020 at 05:38:34PM +0200, Oscar Carter wrote:
> > This patch series checks the return value of vnt_control_out_* function
> > calls.
> >
> > The first patch checks the return value and when necessary modify the
> > function prototype to be able to return the new checked error code.
> >
> > The second patch removes the documentation of functions that their
> > prototype has changed as the function names are clear enought. Also,
> > the actual documentation is not correct in all cases.
> >
> > Changelog v1 -> v2
> > - Remove the function's documentation instead of fix them as suggested
> > Malcolm Priestley.
> >
> > Changelog v2 -> v3
> > - Rebase against the staging-next branch of Greg's staging tree.
>
> Are you sure? It still doesn't apply :(
>
> Please try again.
>
Ok, I will try again.
> thanks,
>
> greg k-h
thanks,
oscar carter
prev parent reply other threads:[~2020-04-25 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 15:38 [PATCH v3 0/2] staging: vt6656: Check the return value of vnt_control_out_* calls Oscar Carter
2020-04-23 15:38 ` [PATCH v3 1/2] " Oscar Carter
2020-04-23 15:38 ` [PATCH v3 2/2] staging: vt6656: Remove functions' documentation Oscar Carter
2020-04-25 10:56 ` [PATCH v3 0/2] staging: vt6656: Check the return value of vnt_control_out_* calls Greg Kroah-Hartman
2020-04-25 13:33 ` Oscar Carter [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=20200425133345.GA3213@ubuntu \
--to=oscar.carter@gmx.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=jbwyatt4@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=tvboxspy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox