On Wed, Nov 08, 2017 at 02:35:05PM -0500, Alex Deucher wrote:
On Wed, Nov 8, 2017 at 2:30 PM, Guenter Roeck groeck@google.com wrote:
On Wed, Nov 8, 2017 at 11:18 AM, Deucher, Alexander
Is this different to "ASoC: amd: Report accurate hw_ptr during dma" which was applied at 16:07?
Yes, this is a fix for that patch. It fixes a 64 bit division that wasn't properly handled.
Ugh. Two problems here. One is obviously that there's a patch that was sent out only a couple of days ago with a whole bunch of tags about internal testing and review and now you've found issues with it. That's worrying.
The other is that you really, really need to get more on top of upstream process. There have been constant problems with this driver and they feel like they're getting worse not better, with the original send of this the noise in the subject lines and body of the e-mail means that what you're sending looks like a case of git send-email CCing people in accidentally rather than a deliberate upstream submission.
The constant problems mean that even as I open the e-mail I'm expecting to have to push back on something which isn't great and affects the way I review things.
In that case, the subject should reflect the problem fixed, the description should describe the problem, and there should be a Fixes: tag pointing to the problematic patch.
I updated the patch subject and added a fixes tag when I resent it after removing the chrome tags. The subject could have been bit better, but I wasn't sure how far to take it since it wasn't my patch originally.
If you're concerned about rewriting commit logs just add a note saying that you did so in the commit log. Please resend normally.