Message ID | 1552426813-9568-1-git-send-email-mikelley@microsoft.com (mailing list archive) |
---|---|
Headers | show |
Series | Drivers: hv: Move Hyper-V clock/timer code to separate clocksource driver | expand |
From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org> Sent: Tuesday, March 12, 2019 2:47 PM > > > > Michael Kelley (2): > > Drivers: hv: Move Hyper-V clockevents code to new clocksource driver > > Drivers: hv: Move Hyper-V clocksource code to new clocksource driver > > You have two different patches that do different things, yet have the > same identical shortlog text :( > > That's not ok, and something that I reject for trivial patches, it > should never happen for a "real" patch as you don't do the same thing in > both of these patches. Hmmm. Not identical. The first patch is "clockevents" code, and the second patch is "clocksource" code. Michael
On Tue, Mar 12, 2019 at 09:53:28PM +0000, Michael Kelley wrote: > From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org> Sent: Tuesday, March 12, 2019 2:47 PM > > > > > > Michael Kelley (2): > > > Drivers: hv: Move Hyper-V clockevents code to new clocksource driver > > > Drivers: hv: Move Hyper-V clocksource code to new clocksource driver > > > > You have two different patches that do different things, yet have the > > same identical shortlog text :( > > > > That's not ok, and something that I reject for trivial patches, it > > should never happen for a "real" patch as you don't do the same thing in > > both of these patches. > > Hmmm. Not identical. The first patch is "clockevents" code, and the second > patch is "clocksource" code. Wow, that's not obvious at all, sorry. You still might want to make it a bit more different :) greg k-h