On Tue, Jan 12, 2021 at 12:09:21PM -0700, Nathan Chancellor wrote: > On Tue, Jan 12, 2021 at 06:48:48PM +0000, Mark Brown wrote: > > This is a random warning fix, why would you expect it to be sent as a > > bug fix? This is the first indication I've seen that anyone is seeing > > it in mainline, in general the people who report and fix warnings are > > doing so based on -next and the patch seems to be from a month ago. I > > don't have this in my inbox so I assume it's applied already or needs to > > be resubmitted anyway. > Well, I consider compiler warnings bugs. I have had plenty of my > compiler warning patches sent as bug fixes for an -rc. Furthermore, this > patch was sent three times by different people, that should give you some > indication that people are tripping over it. I really don't have that good a recall of what warning fixes people are sending, I might notice if I get two versions of the same thing that I look at at roughly the same time but even with a few hours between it's most likely that I'll have completely forgotten. Warning fixes are in general not memorable, it's not a good sign if they are. The default assumption for any warning fix that doesn't say anything else is going to be that either the issue or the toolchain is very new. For any kind of fix if you think that things are in some way urgent you should say something promptly (or provide some indication of this in the submission if you're sending the fix yourself, such as with a fixes tag). If nobody says anything then you should assume that nobody else is going to be aware of any urgency and that this will affect handling. Should it happen that things aren't flagged up then of course do so but consider that this may well be the first time people will be aware there's any urgency, don't assume that people will have been operating with information they didn't have. > The first version was sent on December 11th, it looks like your pull for > 5.11 went on the December 14th, then the second version was applied on > December 16th so I figured it might be destined for 5.11 but I could not > tell (your for-next branch is a merge of your for-5.11 and for-5.12): If it's on the for-5.11 branch then it will be for 5.11, which it must be if it was applied then. If it was and it was applied that long ago it'll already be queued in Takashi's tree and I guess he didn't send it on yet.
Attachment:
signature.asc
Description: PGP signature
