linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"corbet@lwn.net" <corbet@lwn.net>
Subject: Re: [PATCH v2 2/4] PCI: Cleanup comments in setup-bus.c to meet kernel coding style guidelines
Date: Wed, 10 Apr 2019 17:06:03 -0500	[thread overview]
Message-ID: <20190410220603.GL256045@google.com> (raw)
In-Reply-To: <PS2P216MB06428C4318A200E85C590BBC80480@PS2P216MB0642.KORP216.PROD.OUTLOOK.COM>

Hi Nicholas,

On Mon, Mar 11, 2019 at 04:23:23PM +0000, Nicholas Johnson wrote:
> Change block comments to accepted style with asterisks on each line.
> 
> Justify block comments to 80-character limit to reduce the number of
> lines where possible.

Thanks for doing this; I do accept cleanup patches like this.  It does
simplify things if they are last in a series because that makes it
less likely that the "real" patches will cause conflicts.

Don't repost this series just to fix that; I fixed the (trivial)
conflict by hand already.  Just FYI for the future :)

Bjorn

  reply	other threads:[~2019-04-10 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190311162154.3852-1-nicholas.johnson-opensource@outlook.com.au>
2019-03-11 16:23 ` [PATCH v2 1/4] PCI: Consider alignment of hot-added bridges when distributing available resources Nicholas Johnson
2019-03-11 16:23 ` [PATCH v2 2/4] PCI: Cleanup comments in setup-bus.c to meet kernel coding style guidelines Nicholas Johnson
2019-04-10 22:06   ` Bjorn Helgaas [this message]
2019-03-11 16:23 ` [PATCH v2 3/4] PCI: Fix serious bug when sizing bridges with additional size Nicholas Johnson
2019-03-11 16:23 ` [PATCH v2 4/4] PCI: modify kernel parameters to differentiate between MMIO and MMIO_PREF sizes Nicholas Johnson
2019-04-10 22:52   ` Bjorn Helgaas

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=20190410220603.GL256045@google.com \
    --to=helgaas@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=nicholas.johnson-opensource@outlook.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).