> -----Original Message----- > From: Dan Carpenter [mailto:[email protected]] > Sent: Wednesday, August 12, 2015 22:11 > To: Dexuan Cui <[email protected]> > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected] > Subject: Re: [PATCH] Drivers: hv: vmbus: fix init_vp_index() for reloading > hv_netvsc > > On Wed, Aug 12, 2015 at 01:35:07PM +0000, Dexuan Cui wrote: > > > From: Dan Carpenter [mailto:[email protected]] > > > On Wed, Aug 12, 2015 at 12:29:46PM +0000, Dexuan Cui wrote: > > > > > This fixes the recent commit: > > > > > Drivers: hv: vmbus: Further improve CPU affiliation logic > > > > > > Since you are redoing this anyway, include the git hash so we can look > > > it up. In fact, just use the Fixes tag. > > > > > > dan carpenter > > > > Hmm, I didn't read your mail in time and sent out V2 just now... :-) > > > > I'm working on the latest linux-next (next-20150810). > > I didn't add the git hash ID because I think the hash of the patch of the > > same content can be different in different trees (like Greg's tree and > > linux-next)? > > Sometimes it can change, but mostly it doesn't. In this case it didn't. > > The commit hash is based on the tree, the parent, and the content of the > patch description. If we rebase, add a new signed-off-by or merge > the patch through a different tree then the hash changes. > > regards, > dan carpenter
Thanks a lot for the explanation, Dan! I'll remember to add the hash in future. -- Dexuan _______________________________________________ devel mailing list [email protected] http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
