From: "Tobin C. Harding" <me@tobin.cc>
To: Shiva Kerdel <shiva@exdev.nl>
Cc: gregkh@linuxfoundation.org, wsa+renesas@sang-engineering.com,
p.hoefflin@posteo.de, karniksayli1995@gmail.com,
sabitha.george@gmail.com, kdunne@mail.ccsf.edu,
bhumirks@gmail.com, mattkilgore12@gmail.com,
georgiana.chelu93@gmail.com, goudapatilk@gmail.com,
mihaela.muraru21@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Staging: ks7010: ks_*: Use preferred 'u8' kernel type over 'uint8_t'
Date: Wed, 15 Mar 2017 07:33:42 +1100 [thread overview]
Message-ID: <20170314203342.GA24672@eros> (raw)
In-Reply-To: <88746cb4-7df3-f7e4-581a-4266145981b9@exdev.nl>
On Tue, Mar 14, 2017 at 04:12:31PM +0100, Shiva Kerdel wrote:
> Hello Tobin,
>
> I missed the other files because they did not show up using the checkpatch script.
> Next time I will do a recursive search through the files before committing the changes to avoid this situation.
>
> Before I could replay on your message, I got notified of my patches already been merged.
I saw that :)
> However, I am willing to check the other files if you like when I get home and change them too if it's not already done yet.
It's not a big issue, do it only if it pleases you.
>
> Finally it's hard to be descriptive about such changes since the title is very self explaining to me, but
I know, I am finding writing the git log to be the most challenging
part of kernel development so far
Good luck,
Tobin.
prev parent reply other threads:[~2017-03-14 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 2:29 [PATCH 1/3] Staging: ks7010: ks_*: Use preferred 'u8' kernel type over 'uint8_t' Shiva Kerdel
2017-03-12 2:30 ` [PATCH 2/3] Staging: ks7010: ks_hostif.*: Use preferred 'u16' kernel type over 'uint16_t' Shiva Kerdel
2017-03-12 2:30 ` [PATCH 3/3] Staging: ks7010: ks_hostif.*: Use preferred 'u32' kernel type over 'uint32_t' Shiva Kerdel
2017-03-12 3:00 ` [PATCH 1/3] Staging: ks7010: ks_*: Use preferred 'u8' kernel type over 'uint8_t' Tobin C. Harding
2017-03-14 15:12 ` Shiva Kerdel
2017-03-14 20:33 ` Tobin C. Harding [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=20170314203342.GA24672@eros \
--to=me@tobin.cc \
--cc=bhumirks@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=georgiana.chelu93@gmail.com \
--cc=goudapatilk@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=karniksayli1995@gmail.com \
--cc=kdunne@mail.ccsf.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mattkilgore12@gmail.com \
--cc=mihaela.muraru21@gmail.com \
--cc=p.hoefflin@posteo.de \
--cc=sabitha.george@gmail.com \
--cc=shiva@exdev.nl \
--cc=wsa+renesas@sang-engineering.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