From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: linux-pci@vger.kernel.org
Subject: Re: Make Bjorn's life easier (and grease the path of your patch)
Date: Thu, 21 Sep 2023 11:27:10 -0500 [thread overview]
Message-ID: <20230921162710.GA334709@bhelgaas> (raw)
In-Reply-To: <20230921151401.GA25512@wunner.de>
On Thu, Sep 21, 2023 at 05:14:01PM +0200, Lukas Wunner wrote:
> On Thu, Oct 26, 2017 at 05:37:01PM -0500, Bjorn Helgaas wrote:
> ...
> I'm not sure where to insert the Closes tag, checkpatch wants it immediately
> after the Reported-by, but since Closes is like Link, I'd assume that you'd
> prefer it to precede the Reported-by.
I'd put it where checkpatch wants it.
> I've pointed other folks to your message so that they know which guidelines
> to observe when submitting to linux-pci. I'd like to encourage you to
> update it and (if you like) add it to the tree as a maintainer profile
> (see Documentation/maintainer/maintainer-entry-profile.rst) so that it's
> even easier to find.
Yeah, I guess that makes sense. I consider that periodically but I
always hate the fact that we have a dozen different places for
contributors to look for different people's preferences, and I feel
like my preferences are mostly just generic or obvious guidance, so I
hesitate to add another place.
E.g., should we really have to write down that "if the whole file fits
in 80 columns, and your patch adds 100-character lines, you're doing
something wrong"?
But I guess that's just my hubris, and my preferences are not obvious
to everybody else, and having them buried in an old email is not a
real solution, so I should probably just give up and make a maintainer
profile ;)
Bjorn
next prev parent reply other threads:[~2023-09-21 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 22:37 Make Bjorn's life easier (and grease the path of your patch) Bjorn Helgaas
2023-09-21 15:14 ` Lukas Wunner
2023-09-21 16:27 ` Bjorn Helgaas [this message]
2023-09-21 18:44 ` Krzysztof Wilczyński
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230921162710.GA334709@bhelgaas \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox