[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <KL1P15301MB0006C2F8F9E32E736DAB082ABF9C0@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
Date: Mon, 14 May 2018 18:55:50 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Stephen Hemminger <stephen@...workplumber.org>
CC: "kys@...uxonhyperv.com" <kys@...uxonhyperv.com>,
"olaf@...fle.de" <olaf@...fle.de>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@...rosoft.com>,
"apw@...onical.com" <apw@...onical.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"vkuznets@...hat.com" <vkuznets@...hat.com>
Subject: RE: [PATCH 1/1] Drivers: hv: vmbus: enable VMBus protocol version 5.0
> From: Stephen Hemminger <stephen@...workplumber.org>
> Sent: Monday, May 14, 2018 11:18
> To: Dexuan Cui <decui@...rosoft.com>
> > > ...
> > > Hate to pick o the details, but buffer is void * so cast is not necessary here.
> >
> > Yes, it's unnecessary in C, though it's necessary in C++.
> >
> > I found the patch went into char-misc 4 hours ago, so it looks we may
> > as well leave it as is. IMHO an explicit cast is not a bad thing. :-)
> >
> > Thanks,
> > -- Dexuan
>
> Kernel developers like to be concise. In fact there is a smatch script that
> perodically gets run and more cleanup patches get sent.
I checked the "git log" and confimed you're correct: there are a lot of
patches that removed the cast from "void *". :-)
Then let me post a small patch for this.
-- Dexuan
Powered by blists - more mailing lists