From: Wambui Karuga <wambui.karugax@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH 1/5] staging: octeon: remove typedef declaration for cvmx_wqe_t
Date: Fri, 11 Oct 2019 11:59:52 +0300 [thread overview]
Message-ID: <20191011085952.GA9748@wambui> (raw)
In-Reply-To: <alpine.DEB.2.21.1910110817340.2662@hadrien>
On Fri, Oct 11, 2019 at 08:18:25AM +0200, Julia Lawall wrote:
>
>
> On Fri, 11 Oct 2019, Wambui Karuga wrote:
>
> > Remove typedef declaration from struct cvmx_wqe_t in
>
> You can remove the _t from the name as well.
Should I remove the _t from all the enums/structs?
>
> > drivers/staging/octeon/octeon-stubs.h.
>
> It's not really necessary to give the name of the file in the log message,
> as it can easily be seen below.
>
> julia
>
Okay, thought it would be clearer for the commit messages/git log.
Thanks
next prev parent reply other threads:[~2019-10-11 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 6:02 [PATCH 0/5] Remove declarations of new typedef in Wambui Karuga
2019-10-11 6:02 ` [PATCH 1/5] staging: octeon: remove typedef declaration for cvmx_wqe_t Wambui Karuga
2019-10-11 6:18 ` [Outreachy kernel] " Julia Lawall
2019-10-11 8:59 ` Wambui Karuga [this message]
2019-10-11 10:58 ` Dan Carpenter
2019-10-11 6:02 ` [PATCH 2/5] staging: octeon: remove typedef declaration for cvmx_helper_link_info_t Wambui Karuga
2019-10-11 9:02 ` Greg KH
2019-10-11 9:26 ` Wambui Karuga
2019-10-11 6:02 ` [PATCH 3/5] staging: octeon: remove typedef declaration for cvmx_fau_reg_32_t Wambui Karuga
2019-10-11 6:02 ` [PATCH 4/5] staging: octeon: remove typedef declartion for cvmx_pko_command_word0_t Wambui Karuga
2019-10-11 6:02 ` [PATCH 5/5] staging: octeon: remove typedef declaration for cvmx_fau_op_size_t Wambui Karuga
2019-10-11 9:01 ` [PATCH 0/5] Remove declarations of new typedef in Greg KH
2019-10-11 9:24 ` Wambui Karuga
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=20191011085952.GA9748@wambui \
--to=wambui.karugax@gmail.com \
--cc=alpine.DEB.2.21.1910110817340.2662@hadrien \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--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.