https://lwn.net/Articles/722183/ This is a special feed containing comments posted to the individual LWN article titled "4.12 Merge window part 2". en-us Wed, 06 Nov 2024 16:11:53 +0000 Wed, 06 Nov 2024 16:11:53 +0000 https://www.rssboard.org/rss-specification [email protected] https://lwn.net/Articles/722610/ https://lwn.net/Articles/722610/ xtifr <div class="FormattedComment"> Ah, cool, thanks for the elaboration. It's appreciated.<br> </div> Fri, 12 May 2017 20:10:26 +0000 https://lwn.net/Articles/722518/ https://lwn.net/Articles/722518/ fratti <div class="FormattedComment"> <font class="QuotedText">&gt;A bit more about these new things would be great. Can they do anything particularly interesting?</font><br> <p> You can read the data sheets for that. Figuring out what each chip brings to the table would require the author to have knowledge of the entire field these chips are used in. A lot of these drivers are for embedded use cases, so the one who cares about the drivers the most are the hardware vendors and the people building products based on the chips.<br> </div> Fri, 12 May 2017 00:38:44 +0000 https://lwn.net/Articles/722466/ https://lwn.net/Articles/722466/ nevets <div class="FormattedComment"> <font class="QuotedText">&gt; The new "function-fork" tracing option will, when trace events are limited to a specific set of processes, cause any new child processes to be added to the set.</font><br> <p> I should elaborate on this more. This option actually has nothing to do with trace events. It has to do with function tracing. Trace events use the event-fork option, which adds children into the set_event_pid file. This was added in 4.7.<br> <p> The function-fork option does the same for set_ftrace_pid. When a task with a pid in that file forks, its child will be added to the file too, if the option is set. Then the function tracer will also trace the child process.<br> </div> Thu, 11 May 2017 16:36:31 +0000 https://lwn.net/Articles/722433/ https://lwn.net/Articles/722433/ corbet We have pondered adjusting the timing of these articles. For this cycle, we decided to keep the edition timing, but that might well change in the future. <p> The other suggestion is rather harder to act upon. It's quite a bit of work just to come up with the list of newly supported hardware; driver authors, for whatever reason, often do not go out of their way to make that obvious. Trying to document why somebody might be interested in a new pulse-width modulator controller would expand that work considerably. For the most part, the drivers are of interest to somebody who has a computer with that specific device and wants it to work... Thu, 11 May 2017 14:02:35 +0000 https://lwn.net/Articles/722399/ https://lwn.net/Articles/722399/ yodermk <div class="FormattedComment"> I have a couple suggestions for the kernel merge window articles.<br> <p> 1) You've been publishing these on Wednesdays with your weekly edition; that splits it up into three articles -- the second covering a full week of merges but the first and third covering a half a week. The new LWN format lends itself to splitting it up into two equal sections (by time anyway), perhaps published on Monday morning.<br> <p> 2) All the new hardware support. I like it, but would like to see more. A list of the names of things supported means only a little. A bit more about these new things would be great. Can they do anything particularly interesting? Who would care about them -- desktop/laptop/phone users, datacenter managers, single-board computer tinkerers?<br> <p> Thanks!<br> <p> </div> Thu, 11 May 2017 00:14:09 +0000