From: Shiva Kerdel <shiva@exdev.nl>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stuart.yoder@nxp.com, devel@driverdev.osuosl.org,
German.Rivera@freescale.com, nipun.gupta@nxp.com,
linux-kernel@vger.kernel.org, german.rivera@nxp.com,
treding@nvidia.com, itai.katz@nxp.com
Subject: Re: [PATCH v2 1/2] Staging: fsl-mc: include: mc-bus: Kernel type 's16' preferred over 'int16_t'
Date: Thu, 10 Nov 2016 13:33:10 +0100 [thread overview]
Message-ID: <daad9d56-b8e7-d56e-3fee-65e4f346081c@exdev.nl> (raw)
In-Reply-To: <20161110122413.GA7704@kroah.com>
Sorry for this misunderstanding,
Since received a response from Stuart on my previous patch telling me I
was probably working on a out-of-date codebase,
I started to look where I did go wrong.
After some research I found out that I was always one step behind
because I was developing on the actual Linux kernel branch instead
of using the Staging-next as my codebase.
He wrote me to sent the patches that still apply over again with a new
version tag so that's why this patch only contains 2 of them.
I am still new at contributing to the Linux kernel and some things were
not really clear to me at the beginning.
I hope that you could still use these patches and I am trying to avoid
misunderstandings like these.
Do I still need to resend them and is there anything left for me to do
with these?
Best regards,
Shiva Kerdel
On 11/10/16 13:24, Greg KH wrote:
> On Tue, Nov 08, 2016 at 04:42:13PM +0100, Shiva Kerdel wrote:
>> Follow the kernel type preferrences of using 's16' over 'int16_t'.
>>
>> Signed-off-by: Shiva Kerdel <shiva@exdev.nl>
>> ---
>> drivers/staging/fsl-mc/include/mc-bus.h | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
> What is different from your v1 patch?
>
> I'm confused now, I have two different series from you, one 6 patches
> long, and one 2 patches long, claiming to do the same thing.
>
> I've dropped them both from my patch review queue and please, resend
> what you really want me to apply :)
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2016-11-10 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 15:42 Shiva Kerdel
2016-11-08 15:42 ` [PATCH v2 2/2] Staging: fsl-mc: include: mc: Kernel type 's32' preferred over 'int32_t' Shiva Kerdel
2016-11-08 23:52 ` Stuart Yoder
2016-11-08 23:51 ` [PATCH v2 1/2] Staging: fsl-mc: include: mc-bus: Kernel type 's16' preferred over 'int16_t' Stuart Yoder
2016-11-10 12:24 ` Greg KH
2016-11-10 12:33 ` Shiva Kerdel [this message]
2016-11-10 13:16 ` Greg KH
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=daad9d56-b8e7-d56e-3fee-65e4f346081c@exdev.nl \
--to=shiva@exdev.nl \
--cc=German.Rivera@freescale.com \
--cc=devel@driverdev.osuosl.org \
--cc=german.rivera@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=itai.katz@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nipun.gupta@nxp.com \
--cc=stuart.yoder@nxp.com \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®