Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://fosstodon.org/users/kernellogger/statuses/113349909020138144">Thorsten Leemhuis (acct. 1/4) (kernellogger@fosstodon.org)'s status on Wednesday, 23-Oct-2024 01:24:46 JST</a><a href="https://fosstodon.org/@kernellogger" title="kernellogger@fosstodon.org"><img src="https://gnusocial.jp/avatar/109466-48-20230324184559.webp" width="48" height="48" alt="Thorsten Leemhuis (acct. 1/4)" style="position: absolute; left: 0; top: 0;">Thorsten Leemhuis (acct. 1/4)</a><div><a href="https://social.kernel.org/objects/232dc9bb-4cb5-4b8a-8c17-4da6313290b5" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/113726" title="ljs@social.kernel.org">Lorenzo Stoakes</a></li><li><a href="https://gnusocial.jp/user/113727" title="vbabka@social.kernel.org">Vlastimil Babka</a></li></ul></div></section><article><p><a href="https://social.kernel.org/users/ljs">@ljs</a> <a href="https://fosstodon.org/@kees">@kees</a> <a href="https://social.kernel.org/users/vbabka">@vbabka</a> </p><p>Well, good points, but fwiw, afaiui only patches that *were* reviewed by one of the official maintainers are supposed to be included in -next. To quote Stephen from <a href="https://lore.kernel.org/linux-next/20240716083116.27f179bd@canb.auug.org.au/" rel="nofollow noreferrer">https://lore.kernel.org/linux-next/20240716083116.27f179bd@canb.auug.org.au/</a></p><p>"'You will need to ensure that the patches/commits in your tree/series have<br>been:<br>    […]<br>     * reviewed by you (or another maintainer of your subsystem tree),<br>     * successfully unit tested, and <br>     * destined for the current or next Linux merge window."'</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3865347#notice-7557200">In conversation</a><time datetime="2024-10-23T01:24:46+09:00" title="Wednesday, 23-Oct-2024 01:24:46 JST">about a year ago</time> <span>from <span><a href="https://fosstodon.org/@kernellogger/113349909020138144" rel="external" title="Sent from fosstodon.org via ActivityPub">fosstodon.org</a></span></span><a href="https://fosstodon.org/@kernellogger/113349909020138144">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://lore.kernel.org/linux-next/20240716083116.27f179bd@canb.auug.org.au/">Re: update omap branches for linux-next - Stephen Rothwell</a></h5><div></div></header><div></div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Thorsten Leemhuis (acct. 1/4) (kernellogger@fosstodon.org)'s status on Wednesday, 23-Oct-2024 01:24:46 JSTThorsten Leemhuis (acct. 1/4)
in reply to
@ljs @kees @vbabka
Well, good points, but fwiw, afaiui only patches that *were* reviewed by one of the official maintainers are supposed to be included in -next. To quote Stephen from https://lore.kernel.org/linux-next/20240716083116.27f179bd@canb.auug.org.au/
"'You will need to ensure that the patches/commits in your tree/series have
been:
[…]
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window."'
In conversationabout a year ago from fosstodon.orgpermalink
Attachments
1. No result found on File_thumbnail lookup.
  Re: update omap branches for linux-next - Stephen Rothwell

Public

Embed Notice

HTML Code

Corresponding Notice