Re: "Reporting issues" document feedback

2021-04-15 Thread Thorsten Leemhuis
On 14.04.21 15:42, Rafael J. Wysocki wrote: > On Wed, Apr 14, 2021 at 3:22 PM w4v3 wrote: >>> Links to your bug report and the thread on the mailing list would have >>> helped here to understand better what's going on, but whatever, they are >>> not that important. >> Here you go:

[PATCH v1] docs: reporting-issues.rst: CC subsystem and maintainers on regressions

2021-04-15 Thread Thorsten Leemhuis
a difference. Link: https://lore.kernel.org/lkml/dff6badf-58f5-98c8-871c-94d901ac6...@leemhuis.info/ Link: https://lore.kernel.org/lkml/cajz5v0hx2stqvttacihyh-uruh+hi92z9z2zbcngqpt0e2j...@mail.gmail.com/ Signed-off-by: Thorsten Leemhuis --- .../admin-guide/reporting-issues.rst | 49

Re: "Reporting issues" document feedback

2021-04-14 Thread Thorsten Leemhuis
[CCing Rafael] Beforehand: many thx for your feedback and for reporting the bug you faced, much appreciated. On 13.04.21 23:18, w4v3 wrote: > I would like to make some suggestions regarding the "Reporting > issues" document >

Re: [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list

2021-04-09 Thread Thorsten Leemhuis
On 08.04.21 19:31, Jonathan Corbet wrote: > Thorsten Leemhuis writes: > >> +In case you performed a successful bisection, use the title of the change >> that >> +introduced the regression as the second part of your subject. Make the >> report >> +also

[PATCH v2 2/2] docs: reporting-issues: make people CC the regressions list

2021-04-09 Thread Thorsten Leemhuis
Make people CC the recently created mailing list dedicated to Linux kernel regressions when reporting one. Some paragraphs had to be reshuffled and slightly rewritten during the process, as the text otherwise would have gotten unnecessarily hard to follow. Signed-off-by: Thorsten Leemhuis --- v1

[PATCH v2 0/2] Mention regression mailing list in reporting-bugs and MAINTAINERS

2021-04-09 Thread Thorsten Leemhuis
through a different maintainer. Ciao, Thorsten Thorsten Leemhuis (2): MAINTAINERS: add regressions mailing list docs: reporting-issues: make everyone CC the regressions list .../admin-guide/reporting-issues.rst | 55 --- MAINTAINERS

[PATCH v2 1/2] MAINTAINERS: add regressions mailing list

2021-04-09 Thread Thorsten Leemhuis
-regressi...@lists.linux.dev as 'Linux' would have been redundant in the latter case. Signed-off-by: Thorsten Leemhuis --- v1->v2 * use the approach suggested by Greg, which doesn't have a K: entry, but that is likely not much of a help anyway --- MAINTAINERS | 5 + 1 file changed

Re: [RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list

2021-04-07 Thread Thorsten Leemhuis
On 07.04.21 16:56, Greg KH wrote: > On Wed, Apr 07, 2021 at 12:51:43PM +0200, Thorsten Leemhuis wrote: >> On 07.04.21 11:56, Greg KH wrote: >>> On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote: >>>> Add the newly created regression mail

Re: [RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list

2021-04-07 Thread Thorsten Leemhuis
On 07.04.21 12:00, Greg KH wrote: > On Wed, Apr 07, 2021 at 11:21:56AM +0200, Thorsten Leemhuis wrote: >> Make people CC the recently created mailing list dedicated to Linux >> kernel regressions when reporting one. Some paragraphs had to be >> reshuffled and slig

Re: [RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list

2021-04-07 Thread Thorsten Leemhuis
On 07.04.21 11:56, Greg KH wrote: > On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote: >> Add the newly created regression mailing list finally created after it >> already had been agreed on during the maintainers summit 2017 (see >> https://lwn.net/Articles

[RFC PATCH v1 2/2] docs: reporting-issues: make everyone CC the regressions list

2021-04-07 Thread Thorsten Leemhuis
bot.md). Signed-off-by: Thorsten Leemhuis --- Lo! Now that we have a mailing list for regressions I was inclined to remove the "Make the report's subject start with '[REGRESSION]'" part from the text. But in the end I left it, to make it obvious on other lists that the mail is about a

[RFC PATCH v1 0/2] Add regression mailing list with basics for tracking

2021-04-07 Thread Thorsten Leemhuis
to the MAINTAINERS file should better go through a different maintainer. Ciao, Thorsten Thorsten Leemhuis (2): MAINTAINERS: add regressions mailing list docs: reporting-issues: make everyone CC the regressions list .../admin-guide/reporting-issues.rst | 64

[RFC PATCH v1 1/2] MAINTAINERS: add regressions mailing list

2021-04-07 Thread Thorsten Leemhuis
-regressi...@lists.linux.dev as 'Linux' is redundant in the latter case. Signed-off-by: Thorsten Leemhuis --- I was a bit unsure how to add that list to MAINTAINERS. I considered adding a 'M:' with my name and email address there as well, but getting CCed on a lot of regression reports might

Re: [PATCH v2 17/19] docs: replace transation references for reporting-bugs.rst

2021-04-07 Thread Thorsten Leemhuis
On 07.04.21 10:20, Mauro Carvalho Chehab wrote: > Changeset d2ce285378b0 ("docs: make reporting-issues.rst official and delete > reporting-bugs.rst") > dropped reporting-bugs.rst, in favor of reporting-issues.rst, but > translations still need to be updated, in order to point to the > new file. >

Re: [PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst

2021-04-05 Thread Thorsten Leemhuis
On 31.03.21 21:47, Jonathan Corbet wrote: > Greg KH writes: > >> On Tue, Mar 30, 2021 at 04:13:04PM +0200, Thorsten Leemhuis wrote: >>> Removing Documentation/admin-guide/reporting-bugs.rst will break links >>> in some of the translations. I was

Re: [PATCH v1 3/4] docs: reporting-issues.rst: reshuffle and improve TLDR

2021-03-30 Thread Thorsten Leemhuis
Argh, sent this just one hour ago and I already found the first problem: On 30.03.21 16:13, Thorsten Leemhuis wrote: > Make the TLDR a bit shorter while improving it at the same time by going > straight to the aspects readers are more interested it. The change makes > the process especi

[PATCH v1 2/4] MAINTAINERS: add entry for Documentation/admin-guide/reporting-issues.rst

2021-03-30 Thread Thorsten Leemhuis
Thorsten will keep an eye on the new document about reporting issues (aka bugs). Signed-off-by: Thorsten Leemhuis --- MAINTAINERS | 6 ++ 1 file changed, 6 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index e66ff3daf23c..b5d38fedff6c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS

[PATCH v1 3/4] docs: reporting-issues.rst: reshuffle and improve TLDR

2021-03-30 Thread Thorsten Leemhuis
matches the step by step guide better. Signed-off-by: Thorsten Leemhuis --- v1 - Incorporated feedback received from posting a draft to LKML. Also slightly change the beginning of the third paragraph to improve the flow. --- .../admin-guide/reporting-issues.rst | 75 +-- 1

[PATCH v1 4/4] docs: reporting-issues: reduce quoting and assorted fixes

2021-03-30 Thread Thorsten Leemhuis
table maintainers" bits - fix a few typos and mistakes in the text, with a few very small improvements along the way Signed-off-by: Thorsten Leemhuis --- .../admin-guide/reporting-issues.rst | 79 +++ 1 file changed, 45 insertions(+), 34 deletions(-) diff --git a/Doc

[PATCH v1 1/4] docs: make reporting-issues.rst official and delete reporting-bugs.rst

2021-03-30 Thread Thorsten Leemhuis
have been around for a long time. I'm sure over the years you got read a lot and helped quite a few people. But it's time to retire now. Rest in peace. Signed-off-by: Thorsten Leemhuis CC: Harry Wei CC: Alex Shi CC: Federico Vaga CC: Greg KH --- Removing Documentation/admin-guide/reporting

[PATCH v1 0/4] Improve reporting-issues.rst and make it official

2021-03-30 Thread Thorsten Leemhuis
This patchset makes reporting-issues.rst fully official and thus removes reporting-bugs.rst. It also adds an entry for the text in MAINTAINERS as discussed earlier. Then there is the new text for the TLDR already posted as a draft and a patch which assorted fixes and small enhancements. Thorsten

Re: [1/5] reporting-issues: header and TLDR

2021-03-30 Thread Thorsten Leemhuis
On 30.03.21 07:59, Greg KH wrote: > On Mon, Mar 29, 2021 at 04:44:21PM -0600, Jonathan Corbet wrote: >> Thorsten Leemhuis writes: >> >>> FWIW, on another channel someone mentioned the process in the TLDR is >>> quite complicated when it comes to regressions in s

Re: [1/5] reporting-issues: header and TLDR

2021-03-28 Thread Thorsten Leemhuis
On 26.03.21 07:15, Thorsten Leemhuis wrote: > On 26.03.21 07:13, Thorsten Leemhuis wrote: >> >> Lo! Since a few months mainline in >> Documentation/admin-guide/reporting-issues.rst contains a text written >> to obsolete the good old reporting-bugs text. For now, the new

Re: [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 09:59, Greg KH wrote: > On Fri, Mar 26, 2021 at 07:13:09AM +0100, Thorsten Leemhuis wrote: >> >> Lo! Since a few months mainline in >> Documentation/admin-guide/reporting-issues.rst contains a text written >> to obsolete the good old reporting-bugs text

Re: [Ksummit-discuss] [1/5] reporting-issues: header and TLDR

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 07:23, Guenter Roeck wrote: > On 3/25/21 11:15 PM, Thorsten Leemhuis wrote: >> On 26.03.21 07:13, Thorsten Leemhuis wrote: > >> mention if backporting is planed or considered too complex. If backporting >> was > planned ha, of course, thx for pointing it out! Ciao, Thorsten

[5/5] reporting-issues: addendum

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 07:13, Thorsten Leemhuis wrote: > > Lo! Since a few months mainline in > Documentation/admin-guide/reporting-issues.rst contains a text written > to obsolete the good old reporting-bugs text. For now, the new document > still contains a warning at the top that

[4/5] reporting-issues: reference section, stable and longterm sub-processes

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 07:13, Thorsten Leemhuis wrote: > Lo! Since a few months mainline in > Documentation/admin-guide/reporting-issues.rst contains a text written > to obsolete the good old reporting-bugs text. For now, the new document > still contains a warning at the top that basically says

[3/5] reporting-issues: reference section, main guide

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 07:13, Thorsten Leemhuis wrote: > > Lo! Since a few months mainline in > Documentation/admin-guide/reporting-issues.rst contains a text written > to obsolete the good old reporting-bugs text. For now, the new document > still contains a warning at the top that

[2/5] reporting-issues: step-by-step-guide: main and two sub-processes for stable/longterm

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 07:13, Thorsten Leemhuis wrote: > Lo! Since a few months mainline in > Documentation/admin-guide/reporting-issues.rst contains a text written > to obsolete the good old reporting-bugs text. For now, the new document > still contains a warning at the top that basically says

[1/5] reporting-issues: header and TLDR

2021-03-26 Thread Thorsten Leemhuis
On 26.03.21 07:13, Thorsten Leemhuis wrote: > > Lo! Since a few months mainline in > Documentation/admin-guide/reporting-issues.rst contains a text written > to obsolete the good old reporting-bugs text. For now, the new document > still contains a warning at the top that

FYI & RFC: obsoleting reporting-bugs and making reporting-issues official

2021-03-26 Thread Thorsten Leemhuis
Lo! Since a few months mainline in Documentation/admin-guide/reporting-issues.rst contains a text written to obsolete the good old reporting-bugs text. For now, the new document still contains a warning at the top that basically says "this is WIP". But I'd like to remove that warning and delete

Re: [PATCH v3 0/5] docs: reporting-issues: streamline process and solve a FIXME

2021-03-25 Thread Thorsten Leemhuis
On 25.03.21 19:43, Jonathan Corbet wrote: > Thorsten Leemhuis writes: > >> That's why I'd like to speed things up a little. But for that it would >> be good to have something from you: a kind of "I like the direction >> where this patch set is heading and I'm opt

Re: [PATCH v3 0/5] docs: reporting-issues: streamline process and solve a FIXME

2021-03-25 Thread Thorsten Leemhuis
Hi Jonathan! On 19.03.21 20:27, Thorsten Leemhuis wrote: > This series bundle a few patches that piled up for > Documentation/admin-guide/reporting-issues.rst. The main changes are these: Sorry to bring the following up, as I saw you mentioning in another mail on linux-doc you have a lot o

Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-23 Thread Thorsten Leemhuis
On 23.03.21 16:01, Konstantin Ryabitsev wrote: > On Tue, 23 Mar 2021 at 04:58, Thorsten Leemhuis wrote: >>> If we can >>> actually get users to *read* it, I think it's going to save kernel >>> developers a huge amount of time and frustration. >> And users hop

Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-23 Thread Thorsten Leemhuis
On 23.03.21 19:11, Theodore Ts'o wrote: > On Tue, Mar 23, 2021 at 09:57:57AM +0100, Thorsten Leemhuis wrote: >> On 22.03.21 22:56, Theodore Ts'o wrote: >>> On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote: >>>> I agree to the last point and yeah,

Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-23 Thread Thorsten Leemhuis
On 22.03.21 22:56, Theodore Ts'o wrote: > On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote: >> I agree to the last point and yeah, maybe regressions are the more >> important problem we should work on – at least from the perspective of >> kernel development

Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-22 Thread Thorsten Leemhuis
On 22.03.21 17:55, Lukas Bulwahn wrote: > On Mon, Mar 22, 2021 at 4:38 PM Thorsten Leemhuis wrote: >> Lo! I want to provide users with an easier way to search our multitude >> of mailing lists for reports about issues (aka bugs), as reporting the >> same kernel problem mul

Re: RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-22 Thread Thorsten Leemhuis
On 22.03.21 19:32, Linus Torvalds wrote: > On Mon, Mar 22, 2021 at 8:18 AM Thorsten Leemhuis wrote: >> >> I even requested a >> "linux-regressi...@vger.kernel.org" a while later, but didn't hear >> anything back; and, sadly, about the same time I st

Re: RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-22 Thread Thorsten Leemhuis
On 22.03.21 19:34, Eric Wong wrote: > James Bottomley wrote: >> On Mon, 2021-03-22 at 13:16 -0400, Konstantin Ryabitsev wrote: >>> On Mon, Mar 22, 2021 at 04:18:14PM +0100, Thorsten Leemhuis wrote: >>>> Note, there is a second reason why ksummit-discuss is CCed:

RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions

2021-03-22 Thread Thorsten Leemhuis
Lo! I want to provide users with an easier way to search our multitude of mailing lists for reports about issues (aka bugs), as reporting the same kernel problem multiple times has known downsides for everyone involved. That's why I propose to create this new mailing list:

Re: [PATCH v2 2/2] docs: reporting-issues.rst: shortcut for reporting stable regressions

2021-03-19 Thread Thorsten Leemhuis
On 15.03.21 21:11, Jonathan Corbet wrote: > Thorsten Leemhuis writes: > >> Provide a much shorter and easier process for users that deal with >> regressions in stable and longterm kernels, as those should be reported >> quickly. >> >> Signed-off-by: Th

Re: [PATCH v1, RFC] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

2021-03-19 Thread Thorsten Leemhuis
On 16.03.21 18:56, Thorsten Leemhuis wrote: > On 15.03.21 21:20, Jonathan Corbet wrote: >> Thorsten Leemhuis writes: > >> Anything that could be done to >> make it more concise going forward would be more than welcome. > Yeah, will think about it, especially WRT to

[PATCH v3 1/5] docs: reporting-issues.rst: fix small typos and style issues

2021-03-19 Thread Thorsten Leemhuis
Fix a typo and change "head over" to "scroll down", as suggested by Jon when reviewing another patch that used the phrase the same way. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/reporting-issues.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 dele

[PATCH v3 3/5] docs: reporting-issues.rst: reorder some steps

2021-03-19 Thread Thorsten Leemhuis
Reorder some steps where the order in which the readers perform them is not crucial. This is a preparation for a later change that would make the text much more complex otherwise. Content just moved, not changed at all in the process. Signed-off-by: Thorsten Leemhuis --- .../admin-guide

[PATCH v3 0/5] docs: reporting-issues: streamline process and solve a FIXME

2021-03-19 Thread Thorsten Leemhuis
1615116592.git.li...@leemhuis.info/ * initial version, starting straight with v2 to avoid confusion, as one of the patches was submitted earlier already Thorsten Leemhuis (5): docs: reporting-issues.rst: fix small typos and style issues docs: reporting-issues.rst: tone down 'test vanilla mainline

[PATCH v3 4/5] docs: reporting-issues.rst: duplicate sections for reviewing purposes

2021-03-19 Thread Thorsten Leemhuis
This duplicates two section to make the diff in the next patch a bit easier to gasp for humans. Straight copy, no content changes. Signed-off-by: Thorsten Leemhuis --- .../admin-guide/reporting-issues.rst | 184 ++ 1 file changed, 184 insertions(+) diff --git

[PATCH v3 5/5] docs: reporting-issues.rst: improved process esp. for stable regressions

2021-03-19 Thread Thorsten Leemhuis
. That has the additinal benefit that users will search for them quickly when going through the step by step guide and thus will save them trouble if the find reports. Signed-off-by: Thorsten Leemhuis CC: Randy Dunlap --- v3 * s/head over/scroll down/, as suggested by Jon * reduce the amount

[PATCH v3 2/5] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

2021-03-19 Thread Thorsten Leemhuis
bugs, even if they can't test vanilla mainline kernel. Signed-off-by: Thorsten Leemhuis CC: Randy Dunlap --- With this I try to get rid of the last remaining parts that have a 'this needs discussion' box that's in the text. I hope I've found a middle ground that everybody can live with. v2 * fix

Re: [PATCH v1, RFC] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

2021-03-16 Thread Thorsten Leemhuis
On 15.03.21 21:20, Jonathan Corbet wrote: > Thorsten Leemhuis writes: >> Tell users that reporting bugs with vendor kernels which are only >> slightly patched can be okay in some situations, but point out there's a >> risk in doing so. >> >> Adjust some related

[PATCH v1, RFC] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

2021-03-09 Thread Thorsten Leemhuis
bugs, even if they can't test vanilla mainline kernel. Signed-off-by: Thorsten Leemhuis CC: Randy Dunlap --- With this I try to get rid of the last remaining parts that have a 'this needs discussion' box that's in the text. I hope I've found a middle ground that everybody can live with. v1, RFC

[PATCH v2 2/2] docs: reporting-issues.rst: shortcut for reporting stable regressions

2021-03-07 Thread Thorsten Leemhuis
Provide a much shorter and easier process for users that deal with regressions in stable and longterm kernels, as those should be reported quickly. Signed-off-by: Thorsten Leemhuis CC: Randy Dunlap --- v2 * revist, lots of small improvements in various places v1 * https://lore.kernel.org/linux

[PATCH v2 1/2] docs: reporting-issues.rst: move tainted check upwards

2021-03-07 Thread Thorsten Leemhuis
around, no other changes. Signed-off-by: Thorsten Leemhuis --- .../admin-guide/reporting-issues.rst | 84 +-- 1 file changed, 42 insertions(+), 42 deletions(-) diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst

[PATCH v2 0/2] docs: reporting-issues: a easier process for reporting stable regressions

2021-03-07 Thread Thorsten Leemhuis
anyway once the last few details have been sorted out. v2: * inital version, starting straight with v2 to avoid confusion, as one of the patches was submitted earlier already Thorsten Leemhuis (2): docs: reporting-issues.rst: move tainted check upwards docs: reporting-issues.rst: shortcut

[PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-15 Thread Thorsten Leemhuis
. Signed-off-by: Thorsten Leemhuis Reviewed-by: Qais Yousef --- v1->v2 * Fix typo pointed out by Randy * include review feedback from Qais and bis Reviewed-by: v1: https://lore.kernel.org/lkml/20210210054823.242262-1-li...@leemhuis.info/ --- .../admin-guide/reporting-issues.rst |

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-14 Thread Thorsten Leemhuis
Hi! Many thx for looking into this, much appreciated! Am 14.02.21 um 17:00 schrieb Qais Yousef: > On 02/10/21 06:48, Thorsten Leemhuis wrote: > >> - * If the failure includes a stack dump, like an Oops does, consider >> decoding >> - it to find the offending line

Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-14 Thread Thorsten Leemhuis
Am 11.02.21 um 18:07 schrieb Randy Dunlap: > Just a couple of small nits (or one that is repeated): :-D > On 2/9/21 9:48 PM, Thorsten Leemhuis wrote: >> >> - * If the failure includes a stack dump, like an Oops does, consider >> decoding >> - it to f

[PATCH] docs: reporting-issues.rst: shortcut for stable regressions

2021-02-14 Thread Thorsten Leemhuis
Provide a much shorter and easier process for users that deal with regressions in stable and longterm kernels, as those should be reported quickly. Signed-off-by: Thorsten Leemhuis --- .../admin-guide/reporting-issues.rst | 91 --- 1 file changed, 40 insertions(+), 51

[PATCH] docs: reporting-issues.rst: explain how to decode stack traces

2021-02-09 Thread Thorsten Leemhuis
. Signed-off-by: Thorsten Leemhuis --- Reminder: This is not my area of expertise. Hopefully I didn't write anything stupid or omitted something people find important. If I did, please let me know, ideally suggesting what to write; bonus points for people sending text I can simply include in the next

[PATCH] nvme-pci: add quirk to make Kingston A2000 SSD avoid deepest sleep state

2021-01-28 Thread Thorsten Leemhuis
-operational enlat:15000 exlat:15000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- Cc: sta...@vger.kernel.org # 4.14+ Signed-off-by: Thorsten Leemhuis --- Once this is out I will post a link to it in https://bugzilla.kernel.org/show_bug.cgi?id=195039, maybe someone there might be able

[PATCH] docs: process/howto.rst: make sections on bug reporting match practice

2021-01-16 Thread Thorsten Leemhuis
carefully. Signed-off-by: Thorsten Leemhuis --- v1: - kind of a follow up to "[PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org"[1] – I decided to break that idea down into smaller pieces, which I guess is easier for everyone [1] https://lore.kerne

Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

2021-01-12 Thread Thorsten Leemhuis
Thx for your reply and sorry for forgetting to CC you; that was the plan, but I forgot when I called git send-email :-/ Am 11.01.21 um 20:48 wrote Konstantin Ryabitsev: > On Sun, Jan 10, 2021 at 01:10:33PM +0100, Thorsten Leemhuis wrote: >> The front page doesn't make this aspec

Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

2021-01-12 Thread Thorsten Leemhuis
Am 12.01.21 um 00:42 schrieb Randy Dunlap: > On 1/11/21 10:55 AM, Thorsten Leemhuis wrote: >> Am 11.01.21 um 19:14 schrieb Randy Dunlap: >>> On 1/10/21 4:10 AM, Thorsten Leemhuis wrote: > >>> Andrew Morton takes MM bugs and Cc:s them to linux-mm mailing list &g

Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

2021-01-11 Thread Thorsten Leemhuis
Am 11.01.21 um 19:14 schrieb Randy Dunlap: > On 1/10/21 4:10 AM, Thorsten Leemhuis wrote: >> * About 66 of those ~200 components will assign bugs to email addresses >> that look valid, but 125 of them end with @kernel-bugs.osdl.org or >> @kernel-bugs.kernel.org. Those

[PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

2021-01-10 Thread Thorsten Leemhuis
ooked at, thus leave this as it is for now. * A few translations still mention the bug tracker; they hopefully notice this change and follow suit. Signed-off-by: Thorsten Leemhuis --- v1 (RFC): - Just sent to a 'small' audience (linux-docs, Jon, Randy, LKML); once it got some comments

Re: [PATCH] genirq: Export irq_check_status_bit

2020-12-30 Thread Thorsten Leemhuis
Am 30.12.20 um 16:45 schrieb Arnd Bergmann: > From: Arnd Bergmann > > Changing some inline functions to use the new irq_check_status_bit > function out of line breaks calling them from loadable modules: > > ERROR: modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko] > undefined! Just

Re: [PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten")

2020-12-08 Thread Thorsten Leemhuis
Am 08.12.20 um 18:44 schrieb Jonathan Corbet: On Fri, 4 Dec 2020 07:43:47 +0100 Thorsten Leemhuis wrote: This series adds a new and mostly finished document describing how to report issues with the Linux kernel to its developers. OK, I have applied this series. Great, many thx! When I

[PATCH] docs: reporting-issues: move 'outdated, need help' note to proper place

2020-12-08 Thread Thorsten Leemhuis
Move the 'this section is a placeholder for now and needs help by someone with domain knowledge' note one section upwards to the place where it belongs: the 'Decode failure messages' section. Signed-off-by: Thorsten Leemhuis --- Brown paper bag fixup :-/ --- .../admin-guide/reporting

[PATCH v4 3/3] docs: make reporting-bugs.rst obsolete

2020-12-03 Thread Thorsten Leemhuis
. Hence also add a note to reporting-bugs.rst, telling people they're better off reading reporting-issues.rst instead. reporting-bugs.rst is scheduled for removal once reporting-issues.rst is considered ready. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/README.rst

[PATCH v4 1/3] LICENSES: Add the CC-BY-4.0 license

2020-12-03 Thread Thorsten Leemhuis
point that risk out and suggest to only use this license in combination with the GPLv2. [1] https://lkml.kernel.org/r/20201201144314.ga14...@lst.de Signed-off-by: Thorsten Leemhuis CC: Thomas Gleixner CC: Greg Kroah-Hartman CC: Christoph Hellwig --- LICENSES/dual/CC-BY-4.0 | 410

[PATCH v4 2/3] docs: Add a new text describing how to report bugs

2020-12-03 Thread Thorsten Leemhuis
...@lwn.net Signed-off-by: Thorsten Leemhuis CC: Thomas Gleixner CC: Greg Kroah-Hartman CC: Christoph Hellwig --- Documentation/admin-guide/index.rst |1 + .../admin-guide/reporting-issues.rst | 1631 + 2 files changed, 1632 insertions(+) create mode 100644

[PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten")

2020-12-03 Thread Thorsten Leemhuis
t/torvalds/linux.git/log/REPORTING-BUGS Thorsten Leemhuis (3): LICENSES: Add the CC-BY-4.0 license docs: Add a new text describing how to report bugs docs: make reporting-bugs.rst obsolete Documentation/admin-guide/README.rst |4 +- Documentation/admin-guide/bug-bisect.rst |2

Re: [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license

2020-12-01 Thread Thorsten Leemhuis
Am 01.12.20 um 15:43 schrieb Christoph Hellwig: On Mon, Nov 30, 2020 at 07:51:37AM -0700, Jonathan Corbet wrote: @Jonathan: thx for getting the ball rolling again! We could also, if we saw fit, take the position that anything that has been processed through the docs build is a derived

Re: [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license

2020-11-26 Thread Thorsten Leemhuis
Am 24.11.20 um 10:36 schrieb Christoph Hellwig: On Tue, Nov 24, 2020 at 10:31:33AM +0100, Thorsten Leemhuis wrote: Am 24.11.20 um 10:18 schrieb Christoph Hellwig: On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote: For context: Patch 2 of this series adds a text

Re: [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license

2020-11-24 Thread Thorsten Leemhuis
Am 24.11.20 um 13:11 schrieb Matthew Wilcox: On Tue, Nov 24, 2020 at 11:07:41AM +0100, Thorsten Leemhuis wrote: There is nothing special with this text, it's just that GPL is known to not be really ideal for documentation. That makes it hard for people to reuse parts of the docs outside

Re: [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license

2020-11-24 Thread Thorsten Leemhuis
Am 24.11.20 um 10:36 schrieb Christoph Hellwig: On Tue, Nov 24, 2020 at 10:31:33AM +0100, Thorsten Leemhuis wrote: Am 24.11.20 um 10:18 schrieb Christoph Hellwig: On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote: For context: Patch 2 of this series adds a text

Re: [PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license

2020-11-24 Thread Thorsten Leemhuis
Am 24.11.20 um 10:18 schrieb Christoph Hellwig: On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote: For context: Patch 2 of this series adds a text to the Documentation/ directory which (for now) uses "GPL-2.0+ OR CC-BY-4.0", as I want to make it easy and attractive

[PATCH v3 2/3] docs: Add a new text describing how to report bugs

2020-11-24 Thread Thorsten Leemhuis
...@lwn.net Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/index.rst |1 + .../admin-guide/reporting-issues.rst | 1626 + 2 files changed, 1627 insertions(+) create mode 100644 Documentation/admin-guide/reporting-issues.rst diff --git

[PATCH v3 1/3] LICENSES: Add the CC-BY-4.0 license

2020-11-24 Thread Thorsten Leemhuis
/licenses/by/4.0/legalcode.txt Signed-off-by: Thorsten Leemhuis CC: Thomas Gleixner CC: Greg Kroah-Hartman CC: Christoph Hellwig --- For context: Patch 2 of this series adds a text to the Documentation/ directory which (for now) uses "GPL-2.0+ OR CC-BY-4.0", as I want to make it easy and

[PATCH v3 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten")

2020-11-24 Thread Thorsten Leemhuis
mentation/admin-guide/reporting-bugs.rst https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/REPORTING-BUGS Thorsten Leemhuis (3): LICENSES: Add the CC-BY-4.0 license docs: Add a new text describing how to report bugs docs: make reporting-bugs.rst obsolete Documentation/a

[PATCH v3 3/3] docs: make reporting-bugs.rst obsolete

2020-11-24 Thread Thorsten Leemhuis
. Hence also add a note to reporting-bugs.rst, telling people they're better off reading reporting-issues.rst instead. reporting-bugs.rst is scheduled for removal once reporting-issues.rst is considered ready. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/README.rst

Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful

2020-11-21 Thread Thorsten Leemhuis
Am 20.11.20 um 22:58 schrieb Jonathan Corbet: On Fri, 20 Nov 2020 11:46:07 +0100 Thorsten Leemhuis wrote: Am 19.11.20 um 01:29 schrieb Jonathan Corbet: On Sun, 15 Nov 2020 11:13:52 +0100 Thorsten Leemhuis wrote: - Collapse the whole thing down to a patch adding reporting-bugs-v2.rst

Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful

2020-11-20 Thread Thorsten Leemhuis
Am 19.11.20 um 01:29 schrieb Jonathan Corbet: On Sun, 15 Nov 2020 11:13:52 +0100 Thorsten Leemhuis wrote: - Collapse the whole thing down to a patch adding reporting-bugs-v2.rst (or some suitable name). I do wonder if it should also move to the process manual as part

Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful

2020-11-19 Thread Thorsten Leemhuis
Am 19.11.20 um 01:29 schrieb Jonathan Corbet: On Sun, 15 Nov 2020 11:13:52 +0100 Thorsten Leemhuis wrote: So I've not had a chance to try to read through the whole thing again, will try to do so in the near future. Great, thx, looking forward to it. OK, I have made a *quick* pass through

Re: [RFC PATCH v2 08/26] docs: reporting-bugs: make readers check the taint flag

2020-11-19 Thread Thorsten Leemhuis
Am 19.11.20 um 01:05 schrieb Jonathan Corbet: On Thu, 12 Nov 2020 18:58:45 +0100 Thorsten Leemhuis wrote: +If your kernel is tainted, study +:ref:`Documentation/admin-guide/tainted-kernels.rst ` to find +out why. Try to eliminate the reason. Often it's caused by one these three +things: One

Re: [RFC PATCH v2 21/26] docs: reporting-bugs: details on writing and sending the report

2020-11-19 Thread Thorsten Leemhuis
Am 19.11.20 um 01:17 schrieb Jonathan Corbet: On Thu, 12 Nov 2020 18:58:58 +0100 Thorsten Leemhuis wrote: That's also why this commit removes scripts/ver_linux as well: the details it collects are only needed in some situations. And some (a lot?) distributions do not ship it anyway; a better

Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful

2020-11-15 Thread Thorsten Leemhuis
Am 13.11.20 um 23:33 schrieb Jonathan Corbet: On Thu, 12 Nov 2020 18:58:37 +0100 Thorsten Leemhuis wrote: This series rewrites the "how to report bugs to the Linux kernel maintainers" document to make it more straight forward and its essence easier to grasp. At the same time mak

[RFC PATCH v2 04/26] docs: reporting-bugs: step-by-step guide for issues in stable & longterm

2020-11-12 Thread Thorsten Leemhuis
hard to understand. Yet again a reference section will later describe each step in more detail and repeat each step as introduction. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/reporting-bugs.rst | 48 1 file changed, 48 insertions(+) diff --git

[RFC PATCH v2 08/26] docs: reporting-bugs: make readers check the taint flag

2020-11-12 Thread Thorsten Leemhuis
. This approach has a downside: users will later have to check the flag again with the mainline kernel the guide tells them to install. But that is an acceptable trade-off here, as checking only takes a few seconds and can easily prevent wasting time in useless testing and debugging. Signed-off-by: Thorsten

[RFC PATCH v2 03/26] docs: reporting-bugs: step-by-step guide on how to report issues

2020-11-12 Thread Thorsten Leemhuis
the basics right before they do more complicated, time-consuming, and dangerous tasks. Some steps explain a few basics that might seem natural to kernel developers, but are things that people sometimes get wrong. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/reporting-bugs.rst

[RFC PATCH v2 11/26] docs: reporting-bugs: remind people to back up their data

2020-11-12 Thread Thorsten Leemhuis
Add a small reminder that users are best of preparing for emergencies. Doesn't cost us much and might prevent data-loss for a few people, as disabling DKMS, installing mainline and other tasks this guide suggest can break the system if you're unlucky. Signed-off-by: Thorsten Leemhuis

[RFC PATCH v2 15/26] docs: reporting-bugs: make readers test a fresh kernel

2020-11-12 Thread Thorsten Leemhuis
-by: Thorsten Leemhuis --- v2: reshuffled and rewritten to make this section more straight forward = RFC = Am I asking for too much from users by telling them to test mainline? But most will likely have an outdated and heavily patched vendor kernel anyway, so they have to install a vanilla kernel

[RFC PATCH v2 14/26] docs: reporting-bugs: make users write notes, one for each issue

2020-11-12 Thread Thorsten Leemhuis
on one issue, as that is a good time for it: it will make the notes more straight forward if the reader deal with multiple issues at once. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/reporting-bugs.rst | 36 +++- 1 file changed, 27 insertions(+), 9 deletions

[RFC PATCH v2 02/26] docs: reporting-bugs: Create a TLDR how to report issues

2020-11-12 Thread Thorsten Leemhuis
to follow. This TLDR naturally leaves lots of details out. But it will be good enough in some situations, for example for users that recently reported an issue or are familiar with reporting issues to FLOSS projects. Signed-off-by: Thorsten Leemhuis --- v2: reshuffled and rewritten to make

[RFC PATCH v2 05/26] docs: reporting-bugs: begin reference section providing details

2020-11-12 Thread Thorsten Leemhuis
Provide an introduction to the reference section that will provide more details how to report an issue. Mention a few general things here. Those are not strictly needed, but likely wise to write down somewhere. Signed-off-by: Thorsten Leemhuis --- v2: - mention https://jvns.ca/blog/good

[RFC PATCH v2 07/26] docs: reporting-bugs: let users classify their issue

2020-11-12 Thread Thorsten Leemhuis
t;. The alternative would have been: explain each of the three types in the place where it requires special handling for the first time. But that makes it quite easy to miss and harder to find when you need to look it up. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/rep

[RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful

2020-11-12 Thread Thorsten Leemhuis
.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-bugs.rst Commits to it and its predecessor: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/Documentation/admin-guide/reporting-bugs.rst https://git.kernel.org/pub/scm/linux/kernel/git/torva

[RFC PATCH v2 06/26] docs: reporting-bugs: point out we only care about fresh vanilla kernels

2020-11-12 Thread Thorsten Leemhuis
is frustrating for people that invested time in preparing and writing the report. This should help to reduce that. It also explains the reasons, as some users otherwise might think "why do kernel devs makes things so complicated for me". Signed-off-by: Thorsten Leemhuis --- = RFC = Should

[RFC PATCH v2 19/26] docs: reporting-bugs: decode failure messages [need help!]

2020-11-12 Thread Thorsten Leemhuis
? It should answer questions like "when is this actually needed", "what .config options to ideally set to make this step easy or unnecessary (CONFIG_UNWINDER_ORC when available, otherwise CONFIG_UNWINDER_FRAME_POINTER)?". Signed-off-by: Thorsten Leemhuis --- Documentation/a

[RFC PATCH v2 20/26] docs: reporting-bugs: instructions for handling regressions

2020-11-12 Thread Thorsten Leemhuis
. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/bug-bisect.rst | 2 + Documentation/admin-guide/reporting-bugs.rst | 54 2 files changed, 56 insertions(+) diff --git a/Documentation/admin-guide/bug-bisect.rst b/Documentation/admin-guide/bug-bisect.rst

[RFC PATCH v2 12/26] docs: reporting-bugs: tell users to disable DKMS et al.

2020-11-12 Thread Thorsten Leemhuis
Tell users to disable solutions like DKMS to make sure the kernel they install later remains vanilla. The old text did not do that, but such solutions were not that widespread back when it was written. Signed-off-by: Thorsten Leemhuis --- Documentation/admin-guide/reporting-bugs.rst | 22

  1   2   3   4   5   >