public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Lukas Wunner <lukas@wunner.de>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Mehta Sanju <Sanju.Mehta@amd.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] PCI/ACPI: PCI/ACPI: Validate devices with power resources support D3
Date: Thu, 27 Oct 2022 15:44:01 -0500	[thread overview]
Message-ID: <20221027204401.GA838114@bhelgaas> (raw)
In-Reply-To: <7ba39e79-7fe5-a644-83da-c8fc05a1ca84@amd.com>

On Thu, Oct 27, 2022 at 02:56:19PM -0500, Limonciello, Mario wrote:
> On 10/27/2022 00:24, Lukas Wunner wrote:
> > ...

> > I think git.kernel.org links are preferred to 3rd party hosting services.
> 
> I wasn't aware of any such policy.  Within the last release it seemed to me
> Github was perfectly acceptable to use for links.
> 
> $ git log v6.0..v6.1-rc1 | grep "Link: https://github" | wc -l
> 107
> $ git log v6.0..v6.1-rc1 | grep "Link: https://git.kernel.org" | wc -l
> 2

I'm not aware of a formal policy, but I do prefer kernel.org links
because github is a 3rd party company that may not persist, may add
ads, etc.  I know github may *also* add value like fancier markup,
cross referencing, CI services, etc., but for commit logs, the
longevity of kernel.org is pretty persuasive to me.

There's a similar situation with mailing lists where many of the old
links to archives like marc.info, spinics.net, lkml.org, etc., are now
dead or not as useful for building tools (b4, for instance).

So no big deal, but I would probably silently convert them when
applying.  The current formats I use are:

  commits: https://git.kernel.org/linus/dff6139015dc
  files:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/pci-acpi.c?id=v6.0#n976

Bjorn

      reply	other threads:[~2022-10-27 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 21:52 [PATCH v4] PCI/ACPI: PCI/ACPI: Validate devices with power resources support D3 Mario Limonciello
2022-10-27  5:24 ` Lukas Wunner
2022-10-27 19:56   ` Limonciello, Mario
2022-10-27 20:44     ` Bjorn Helgaas [this message]

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=20221027204401.GA838114@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Sanju.Mehta@amd.com \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    /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