ACK/cmnt: [SRU][Yakkety][Zesty][PATCH 0/2] Fixes for LP:1630924

[Stefan Bader]

On 30.01.2017 15:47, Joseph Salisbury wrote:
> On 01/30/2017 06:10 AM, Stefan Bader wrote:
>> Again, not sure but maybe wants some SAUCE tagging for not being in upstream
>> tree....
>>
>> -Stefan
>>
>>
>>
> The first is commit 59107e2f4 is in mainline as of 4.10-rc1.  The second commit, 56ef6718a1d8, is not in mainline as of yet, but it is in linux-next.  
> 
> For future reference, should commits in linux-next be tagged as SAUCE?
> 
> Joe
> 
> 
As I wrote in the other reply, I am not completely sure about the exact format.
I am trying to think what would help me if I were to apply an upstream stable
patchset. So I am wondering about some easy to type keyword which I could search
the git log for in order to find things that might need reverting.
These two are a bit special, too. The first is upstream but not tagged for
stable, the second one is in next and tagged for stable, so there is a good
chance that both will come via an upstream stable patchset at some point.

SAUCE for SRU seems to say it is something we do not expect to be coming via
upstream stable, which might be wrong.

-Stefan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20170130/ace4153c/attachment.sig>