From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-pci@vger.kernel.org, robh@kernel.org, kishon@ti.com,
kw@linux.com, bhelgaas@google.com
Subject: Re: AFK till mid-July
Date: Tue, 24 May 2022 10:07:18 -0500 [thread overview]
Message-ID: <20220524150718.GA243159@bhelgaas> (raw)
In-Reply-To: <20220524105915.GA14773@lpieralisi>
On Tue, May 24, 2022 at 11:59:15AM +0100, Lorenzo Pieralisi wrote:
> Dear PCI developers,
>
> I wanted to make everyone aware I will be AFK till mid-July and won't be
> able to carry out patches review and queuing as usual.
>
> I notified Bjorn and Rob who will kindly help (best-effort) in my
> absence - please be patient and we will handle the backlog in the
> next few months.
I'm not as versed in the pci/controllers/ code as Rob and Lorenzo, so
it will take me longer to review things, and I apologize in advance.
When I *do* review patches there, one of my main tools is to compare
with other similar drivers. If a driver is structured the same way as
others and uses the same naming conventions, that's a huge help to me.
I also pay attention to the mundane details like coding style, commit
logs (both content and formatting), subject lines, etc. Patches that
look like they fit with prior history and style are also a big help to
me.
My goal is not just to be OCD about it, but to make drivers/pci/
generally uniform and more pleasant for those who come after us.
Commits are "write once, read many" things, so I want to optimize for
the readers, not the writer.
Old posting of hints, which is still relevant:
https://lore.kernel.org/r/20171026223701.GA25649@bhelgaas-glaptop.roam.corp.google.com
prev parent reply other threads:[~2022-05-24 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 10:59 AFK till mid-July Lorenzo Pieralisi
2022-05-24 15:07 ` 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=20220524150718.GA243159@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).