From: Stefano Brivio <sbrivio@redhat.com>
To: Briana Oursler <briana.oursler@gmail.com>
Cc: julia.lawall@inria.fr, gregkh@linuxfoundation.org,
forest@alittletooquiet.net, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [Patch v2 0/3] staging: vt6655: Remove functions that are never
Date: Tue, 31 Mar 2020 21:09:46 +0200 [thread overview]
Message-ID: <20200331210823.50dbe9be@elisabeth> (raw)
In-Reply-To: <cover.1585630805.git.briana.oursler@gmail.com>
> Subject: [Outreachy kernel] [Patch v2 0/3] staging: vt6655: Remove functions that are never
never...? :)
On Mon, 30 Mar 2020 22:16:37 -0700
Briana Oursler <briana.oursler@gmail.com> wrote:
> This patchset removes functions that are not called in the driver but
> are prototyped in card.h. Each commit limits its scope to one function
> definition and related documentation in code. References in the
> developer's initial changelog were left in place.
What do you mean by this? Which references?
--
Stefano
next prev parent reply other threads:[~2020-03-31 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 5:16 [Patch v2 0/3] staging: vt6655: Remove functions that are never Briana Oursler
2020-03-31 5:16 ` [Patch v2 1/3] Staging: vt6655: Remove CARDbSoftwareReset definition Briana Oursler
2020-03-31 5:16 ` [Patch v2 2/3] Staging: vt6655: Remove CARDvSetLoopbackMode definition Briana Oursler
2020-03-31 5:16 ` [Patch v2 3/3] Staging: vt6655: Remove CARDbRadioPowerOn definition Briana Oursler
2020-03-31 19:09 ` Stefano Brivio [this message]
2020-03-31 19:42 ` [Outreachy kernel] [Patch v2 0/3] staging: vt6655: Remove functions that are never Briana Oursler
2020-03-31 20:04 ` Julia Lawall
2020-03-31 20:09 ` Briana Oursler
2020-03-31 20:22 ` Julia Lawall
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=20200331210823.50dbe9be@elisabeth \
--to=sbrivio@redhat.com \
--cc=briana.oursler@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=outreachy-kernel@googlegroups.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.