[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgUVHucyjp6M7qmn8b=aqwucfS4SQpqOCR5sKr16zoO5g@mail.gmail.com>
Date: Wed, 11 May 2022 08:55:34 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Theodore Ts'o" <tytso@....edu>
Cc: Borislav Petkov <bp@...en8.de>,
Thorsten Leemhuis <linux@...mhuis.info>,
Thomas Gleixner <tglx@...utronix.de>,
Zhangfei Gao <zhangfei.gao@...mail.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: Link: tag and links to submission and reports (was: Re: [GIT
pull] core/urgent for v5.18-rc6)
On Wed, May 11, 2022 at 8:50 AM Theodore Ts'o <tytso@....edu> wrote:
>
> I would argue that it should be the patch submitter's responsibility
> to explicitly add a URL to the problem report.
I agree in the perfect case.
But in practice, we have a lot more patch submitters than we have
maintainers, and not all "leaf developers" necessarily know how to do
everything.
So the maintainer should probably expect to fix things up. Not always,
but also not a "the developer should have done this, so I won't do it"
This isn't so different from the fact that not everybody writes
English proficiently - people do hopefully end up fixing things up as
they get passed onwards.
Linus
Powered by blists - more mailing lists