Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1480011 > unrolled thread
| Started by | Michael Opdenacker <michael.opdenacker@free-electrons.com> |
|---|---|
| First post | 2016-09-09 15:50 +0200 |
| Last post | 2016-09-15 16:50 +0200 |
| Articles | 9 — 4 participants |
Back to article view | Back to linux.kernel
[PATCH] documentation: fix broken lkml archive links in RCU requirements Michael Opdenacker <michael.opdenacker@free-electrons.com> - 2016-09-09 15:50 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Richard Weinberger <richard.weinberger@gmail.com> - 2016-09-09 16:20 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-09-09 16:40 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Michael Opdenacker <michael.opdenacker@free-electrons.com> - 2016-09-15 14:10 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Steven Rostedt <rostedt@goodmis.org> - 2016-09-09 16:40 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Michael Opdenacker <michael.opdenacker@free-electrons.com> - 2016-09-15 14:10 +0200
[PATCH] documentation: fix broken lkml archive links in RCU requirements Michael Opdenacker <michael.opdenacker@free-electrons.com> - 2016-09-15 14:20 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements Steven Rostedt <rostedt@goodmis.org> - 2016-09-15 15:20 +0200
Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-09-15 16:50 +0200
| From | Michael Opdenacker <michael.opdenacker@free-electrons.com> |
|---|---|
| Date | 2016-09-09 15:50 +0200 |
| Subject | [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <sfulQ-3ra-33@gated-at.bofh.it> |
Fix 4 LKML archive links that became broken (data loss on mail-archive.com?) Working links were found on Paul McKenney's RCU articles on LWN.net, from which the documentation originates: http://lwn.net/Articles/652156/ http://lwn.net/Articles/652677/ http://lwn.net/Articles/653326/ Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> --- Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html index ece410f40436..2adb3d43ce44 100644 --- a/Documentation/RCU/Design/Requirements/Requirements.html +++ b/Documentation/RCU/Design/Requirements/Requirements.html @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> efforts, memory footprint is critically important on single-CPU systems with non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> +<a href="http://lkml.org/lkml/2009/1/14/449">tiny RCU</a> was born. Josh Triplett has since taken over the small-memory banner with his <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: and cleaned up with <tt>destroy_rcu_head()</tt>. Mathieu Desnoyers made me aware of this requirement, and also supplied the needed - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. + <a href="https://lkml.org/lkml/2010/3/18/417">patch</a>. <li> An infinite loop in an RCU read-side critical section will eventually trigger an RCU CPU stall warning splat, with the duration of “eventually” being controlled by the @@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option. <p> This all should be quite obvious, but the fact remains that Linus Torvalds recently had to -<a href="https://lkml.kernel.org/g/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> +<a href="https://lkml.org/lkml/2015/4/14/616">remind</a> me of this requirement. <h3><a name="Firmware Interface">Firmware Interface</a></h3> @@ -2229,7 +2229,7 @@ Thankfully, RCU update-side primitives, including The name notwithstanding, some Linux-kernel architectures can have nested NMIs, which RCU must handle correctly. Andy Lutomirski -<a href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> +<a href="https://lkml.org/lkml/2014/11/21/642">surprised me</a> with this requirement; he also kindly surprised me with <a href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a> -- 2.7.4
[toc] | [next] | [standalone]
| From | Richard Weinberger <richard.weinberger@gmail.com> |
|---|---|
| Date | 2016-09-09 16:20 +0200 |
| Message-ID | <sfuOS-3Q2-9@gated-at.bofh.it> |
| In reply to | #1480011 |
Michael, On Fri, Sep 9, 2016 at 3:43 PM, Michael Opdenacker <michael.opdenacker@free-electrons.com> wrote: > Fix 4 LKML archive links that became broken (data loss > on mail-archive.com?) > > Working links were found on Paul McKenney's RCU articles > on LWN.net, from which the documentation originates: > http://lwn.net/Articles/652156/ > http://lwn.net/Articles/652677/ > http://lwn.net/Articles/653326/ > > Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> > --- > Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html > index ece410f40436..2adb3d43ce44 100644 > --- a/Documentation/RCU/Design/Requirements/Requirements.html > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's > <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> > efforts, memory footprint is critically important on single-CPU systems with > non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus > -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > +<a href="http://lkml.org/lkml/2009/1/14/449">tiny RCU</a> > was born. > Josh Triplett has since taken over the small-memory banner with his > <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: > and cleaned up with <tt>destroy_rcu_head()</tt>. > Mathieu Desnoyers made me aware of this requirement, and also > supplied the needed > - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. > + <a href="https://lkml.org/lkml/2010/3/18/417">patch</a>. Please don't add lkml.org. It does not use message ids for indexing. With knowing the message id you can query any other archive. e.g. http://marc.info/?i=20100319013024.GA28456@Krystal By adding lkml.org you kill that information. Archives come and go, the message id is the only common query id we have. IMHO kernel.org admins should fix/improve their redirection service to point to a working service. -- Thanks, //richard
[toc] | [prev] | [next] | [standalone]
| From | "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> |
|---|---|
| Date | 2016-09-09 16:40 +0200 |
| Subject | Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <sfv8d-45z-11@gated-at.bofh.it> |
| In reply to | #1480037 |
On Fri, Sep 09, 2016 at 04:17:14PM +0200, Richard Weinberger wrote: > Michael, > > On Fri, Sep 9, 2016 at 3:43 PM, Michael Opdenacker > <michael.opdenacker@free-electrons.com> wrote: > > Fix 4 LKML archive links that became broken (data loss > > on mail-archive.com?) > > > > Working links were found on Paul McKenney's RCU articles > > on LWN.net, from which the documentation originates: > > http://lwn.net/Articles/652156/ > > http://lwn.net/Articles/652677/ > > http://lwn.net/Articles/653326/ > > > > Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> > > --- > > Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html > > index ece410f40436..2adb3d43ce44 100644 > > --- a/Documentation/RCU/Design/Requirements/Requirements.html > > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > > @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's > > <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> > > efforts, memory footprint is critically important on single-CPU systems with > > non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus > > -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > > +<a href="http://lkml.org/lkml/2009/1/14/449">tiny RCU</a> > > was born. > > Josh Triplett has since taken over the small-memory banner with his > > <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> > > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: > > and cleaned up with <tt>destroy_rcu_head()</tt>. > > Mathieu Desnoyers made me aware of this requirement, and also > > supplied the needed > > - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. > > + <a href="https://lkml.org/lkml/2010/3/18/417">patch</a>. > > Please don't add lkml.org. It does not use message ids for indexing. > With knowing the message id you can query any other archive. > e.g. http://marc.info/?i=20100319013024.GA28456@Krystal > By adding lkml.org you kill that information. Archives come and go, > the message id is the only common query id we have. > > IMHO kernel.org admins should fix/improve their redirection service to > point to a working service. There has been some instability in the kernel.org redirection. Right now, the /r/ services seems to work, though as noted the /g/ does not. Please report this to the Kernel.org administrators: https://kernel.org/category/contact-us.html Thanx, Paul
[toc] | [prev] | [next] | [standalone]
| From | Michael Opdenacker <michael.opdenacker@free-electrons.com> |
|---|---|
| Date | 2016-09-15 14:10 +0200 |
| Subject | Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <shDEl-6P5-7@gated-at.bofh.it> |
| In reply to | #1480065 |
Richard, Paul, Thank you for your replies! On 09/09/2016 16:33, Paul E. McKenney wrote: > On Fri, Sep 09, 2016 at 04:17:14PM +0200, Richard Weinberger wrote: > Please don't add lkml.org. It does not use message ids for indexing. > With knowing the message id you can query any other archive. > e.g. http://marc.info/?i=20100319013024.GA28456@Krystal > By adding lkml.org you kill that information. Archives come and go, > the message id is the only common query id we have. > > IMHO kernel.org admins should fix/improve their redirection service to > point to a working service. > There has been some instability in the kernel.org redirection. Right > now, the /r/ services seems to work, though as noted the /g/ does not. > Please report this to the Kernel.org administrators: > > https://kernel.org/category/contact-us.html > > Thanx, Paul Done. I reported this issue to them and will keep an eye on it. I definitely agree that we shouldn't use the message ids. Otherwise, that's really a lot of detective work to find out which message was referred to. That's very good advise. Thanks, Michael. -- Michael Opdenacker, CEO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
[toc] | [prev] | [next] | [standalone]
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Date | 2016-09-09 16:40 +0200 |
| Subject | Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <sfv8d-45z-19@gated-at.bofh.it> |
| In reply to | #1480037 |
On Fri, 9 Sep 2016 16:17:14 +0200 Richard Weinberger <richard.weinberger@gmail.com> wrote: > > Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> > > --- > > Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html > > index ece410f40436..2adb3d43ce44 100644 > > --- a/Documentation/RCU/Design/Requirements/Requirements.html > > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > > @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's > > <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> > > efforts, memory footprint is critically important on single-CPU systems with > > non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus > > -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > > +<a href="http://lkml.org/lkml/2009/1/14/449">tiny RCU</a> > > was born. > > Josh Triplett has since taken over the small-memory banner with his > > <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> > > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: > > and cleaned up with <tt>destroy_rcu_head()</tt>. > > Mathieu Desnoyers made me aware of this requirement, and also > > supplied the needed > > - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. > > + <a href="https://lkml.org/lkml/2010/3/18/417">patch</a>. > > Please don't add lkml.org. It does not use message ids for indexing. > With knowing the message id you can query any other archive. > e.g. http://marc.info/?i=20100319013024.GA28456@Krystal > By adding lkml.org you kill that information. Archives come and go, > the message id is the only common query id we have. > > IMHO kernel.org admins should fix/improve their redirection service to > point to a working service. > Correct, we avoid any links to lkml.org at all costs. Simple do a s,/g/,/r/, and all your links should work. For example, using the above mentioned link: https://lkml.kernel.org/r/20100319013024.GA28456@Krystal Works as expected. -- Steve
[toc] | [prev] | [next] | [standalone]
| From | Michael Opdenacker <michael.opdenacker@free-electrons.com> |
|---|---|
| Date | 2016-09-15 14:10 +0200 |
| Subject | Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <shDEn-6P5-55@gated-at.bofh.it> |
| In reply to | #1480070 |
Hi Steve, On 09/09/2016 16:34, Steven Rostedt wrote: > Correct, we avoid any links to lkml.org at all costs. Simple do a > > s,/g/,/r/, and all your links should work. For example, using the above > mentioned link: > > https://lkml.kernel.org/r/20100319013024.GA28456@Krystal > > Works as expected. I confirm that all the links work indeed. I'm sending a patch update right away. Thanks! Michael. -- Michael Opdenacker, CEO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
[toc] | [prev] | [next] | [standalone]
| From | Michael Opdenacker <michael.opdenacker@free-electrons.com> |
|---|---|
| Date | 2016-09-15 14:20 +0200 |
| Message-ID | <shDO2-6VP-33@gated-at.bofh.it> |
| In reply to | #1484070 |
Fix 4 LKML archive links that became broken (issue with https://lkml.kernel.org/g/ redirection links) Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> --- Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html index ece410f40436..1c39a2362911 100644 --- a/Documentation/RCU/Design/Requirements/Requirements.html +++ b/Documentation/RCU/Design/Requirements/Requirements.html @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> efforts, memory footprint is critically important on single-CPU systems with non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> +<a href="https://lkml.kernel.org/r/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> was born. Josh Triplett has since taken over the small-memory banner with his <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: and cleaned up with <tt>destroy_rcu_head()</tt>. Mathieu Desnoyers made me aware of this requirement, and also supplied the needed - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. + <a href="https://lkml.kernel.org/r/20100319013024.GA28456@Krystal">patch</a>. <li> An infinite loop in an RCU read-side critical section will eventually trigger an RCU CPU stall warning splat, with the duration of “eventually” being controlled by the @@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option. <p> This all should be quite obvious, but the fact remains that Linus Torvalds recently had to -<a href="https://lkml.kernel.org/g/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> +<a href="https://lkml.kernel.org/r/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> me of this requirement. <h3><a name="Firmware Interface">Firmware Interface</a></h3> @@ -2229,7 +2229,7 @@ Thankfully, RCU update-side primitives, including The name notwithstanding, some Linux-kernel architectures can have nested NMIs, which RCU must handle correctly. Andy Lutomirski -<a href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> +<a href="https://lkml.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> with this requirement; he also kindly surprised me with <a href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a> -- 2.7.4
[toc] | [prev] | [next] | [standalone]
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Date | 2016-09-15 15:20 +0200 |
| Subject | Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <shEK6-7vq-9@gated-at.bofh.it> |
| In reply to | #1484093 |
On Thu, 15 Sep 2016 14:17:06 +0200 Michael Opdenacker <michael.opdenacker@free-electrons.com> wrote: > Fix 4 LKML archive links that became broken > (issue with https://lkml.kernel.org/g/ redirection links) > > Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> > --- > Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html > index ece410f40436..1c39a2362911 100644 > --- a/Documentation/RCU/Design/Requirements/Requirements.html > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's > <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> > efforts, memory footprint is critically important on single-CPU systems with > non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus > -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > +<a href="https://lkml.kernel.org/r/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > was born. > Josh Triplett has since taken over the small-memory banner with his > <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: > and cleaned up with <tt>destroy_rcu_head()</tt>. > Mathieu Desnoyers made me aware of this requirement, and also > supplied the needed > - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. > + <a href="https://lkml.kernel.org/r/20100319013024.GA28456@Krystal">patch</a>. > <li> An infinite loop in an RCU read-side critical section will > eventually trigger an RCU CPU stall warning splat, with > the duration of “eventually” being controlled by the > @@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option. > <p> > This all should be quite obvious, but the fact remains that > Linus Torvalds recently had to > -<a href="https://lkml.kernel.org/g/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> > +<a href="https://lkml.kernel.org/r/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> > me of this requirement. > > <h3><a name="Firmware Interface">Firmware Interface</a></h3> > @@ -2229,7 +2229,7 @@ Thankfully, RCU update-side primitives, including > The name notwithstanding, some Linux-kernel architectures > can have nested NMIs, which RCU must handle correctly. > Andy Lutomirski > -<a href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> > +<a href="https://lkml.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> > with this requirement; > he also kindly surprised me with > <a href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a> Strange that this one still works. Anyway... Acked-by: Steven Rostedt <rostedt@goodmis.org> -- Steve
[toc] | [prev] | [next] | [standalone]
| From | "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> |
|---|---|
| Date | 2016-09-15 16:50 +0200 |
| Subject | Re: [PATCH] documentation: fix broken lkml archive links in RCU requirements |
| Message-ID | <shG9c-8fB-31@gated-at.bofh.it> |
| In reply to | #1484151 |
On Thu, Sep 15, 2016 at 09:18:28AM -0400, Steven Rostedt wrote: > On Thu, 15 Sep 2016 14:17:06 +0200 > Michael Opdenacker <michael.opdenacker@free-electrons.com> wrote: > > > Fix 4 LKML archive links that became broken > > (issue with https://lkml.kernel.org/g/ redirection links) > > > > Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com> > > --- > > Documentation/RCU/Design/Requirements/Requirements.html | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html > > index ece410f40436..1c39a2362911 100644 > > --- a/Documentation/RCU/Design/Requirements/Requirements.html > > +++ b/Documentation/RCU/Design/Requirements/Requirements.html > > @@ -1527,7 +1527,7 @@ However, as I learned from Matt Mackall's > > <a href="http://elinux.org/Linux_Tiny-FAQ">bloatwatch</a> > > efforts, memory footprint is critically important on single-CPU systems with > > non-preemptible (<tt>CONFIG_PREEMPT=n</tt>) kernels, and thus > > -<a href="https://lkml.kernel.org/g/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > > +<a href="https://lkml.kernel.org/r/20090113221724.GA15307@linux.vnet.ibm.com">tiny RCU</a> > > was born. > > Josh Triplett has since taken over the small-memory banner with his > > <a href="https://tiny.wiki.kernel.org/">Linux kernel tinification</a> > > @@ -1975,7 +1975,7 @@ guard against mishaps and misuse: > > and cleaned up with <tt>destroy_rcu_head()</tt>. > > Mathieu Desnoyers made me aware of this requirement, and also > > supplied the needed > > - <a href="https://lkml.kernel.org/g/20100319013024.GA28456@Krystal">patch</a>. > > + <a href="https://lkml.kernel.org/r/20100319013024.GA28456@Krystal">patch</a>. > > <li> An infinite loop in an RCU read-side critical section will > > eventually trigger an RCU CPU stall warning splat, with > > the duration of “eventually” being controlled by the > > @@ -2088,7 +2088,7 @@ be hidden behind a <tt>CONFIG_RCU_EXPERT</tt> <tt>Kconfig</tt> option. > > <p> > > This all should be quite obvious, but the fact remains that > > Linus Torvalds recently had to > > -<a href="https://lkml.kernel.org/g/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> > > +<a href="https://lkml.kernel.org/r/CA+55aFy4wcCwaL4okTs8wXhGZ5h-ibecy_Meg9C4MNQrUnwMcg@mail.gmail.com">remind</a> > > me of this requirement. > > > > <h3><a name="Firmware Interface">Firmware Interface</a></h3> > > @@ -2229,7 +2229,7 @@ Thankfully, RCU update-side primitives, including > > The name notwithstanding, some Linux-kernel architectures > > can have nested NMIs, which RCU must handle correctly. > > Andy Lutomirski > > -<a href="https://lkml.kernel.org/g/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> > > +<a href="https://lkml.kernel.org/r/CALCETrXLq1y7e_dKFPgou-FKHB6Pu-r8+t-6Ds+8=va7anBWDA@mail.gmail.com">surprised me</a> > > with this requirement; > > he also kindly surprised me with > > <a href="https://lkml.kernel.org/g/CALCETrXSY9JpW3uE6H8WYk81sg56qasA2aqmjMPsq5dOtzso=g@mail.gmail.com">an algorithm</a> > > Strange that this one still works. Anyway... > > > Acked-by: Steven Rostedt <rostedt@goodmis.org> So we are confident that these links won't be fixed by the next merge window? Thanx, Paul
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web