public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Ni, Ruiyu" <ruiyu.ni@Intel.com>, Heyi Guo <heyi.guo@linaro.org>,
	edk2-devel@lists.01.org
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	Julien Grall <julien.grall@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v5 2/6] OvmfPkg/PciHostBridgeLib: Init PCI aperture to 0
Date: Fri, 2 Mar 2018 11:08:01 +0100	[thread overview]
Message-ID: <5fdaa2e0-442c-04cd-e362-659abce87438@redhat.com> (raw)
In-Reply-To: <001017d1-42ae-8376-6410-3f6f34f6c3f5@Intel.com>

On 03/01/18 13:03, Ni, Ruiyu wrote:
> On 3/1/2018 6:20 PM, Laszlo Ersek wrote:
>> On 03/01/18 07:57, Heyi Guo wrote:
>>> Use ZeroMem to initialize all fields in temporary
>>> PCI_ROOT_BRIDGE_APERTURE variables to zero. This is not mandatory but
>>> is helpful for future extension: when we add new fields to
>>> PCI_ROOT_BRIDGE_APERTURE and the default value of these fields can
>>> safely be zero, this code will not suffer from an additional
>>> change.
>>>
>>> Contributed-under: TianoCore Contribution Agreement 1.1
>>> Signed-off-by: Heyi Guo <heyi.guo@linaro.org>
>>>
>>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>>> Cc: Anthony Perard <anthony.perard@citrix.com>
>>> Cc: Julien Grall <julien.grall@linaro.org>
>>> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
>>> Cc: Laszlo Ersek <lersek@redhat.com>
>>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>> ---
>>>   OvmfPkg/Library/PciHostBridgeLib/PciHostBridgeLib.c | 4 ++++
>>>   OvmfPkg/Library/PciHostBridgeLib/XenSupport.c       | 5 +++++
>>>   2 files changed, 9 insertions(+)
>>
>> I also suggest a different subject line:
>>
>> OvmfPkg/PciHostBridgeLib: clear PCI_ROOT_BRIDGE_APERTURE vars for
>> (re)init
>>
>> (74 chars)
> 
> I sometimes tries very hard to make the subject line be <= 70 chars.
> 74 is acceptable?

To my knowledge, the Linux kernel development guidelines suggest
wrapping the commit message body at 74 characters, and IIRC the same
limit applies to the subject line. I tend to follow these ideas for edk2
development too.

I think anything under 74 chars (for the subject) is an unreasonable
expectation for edk2. First, we start with a prefix of the form

  XxxPkg/Module: ...

Sometimes this prefix is incredibly long alread :/ So what I do (and I
guess most others do as well) is that I first write an "honest" subject
line (which frequently reaches 90-100 chars), and then work on
compressing it down to 74 characters. Sometimes it becomes a real
struggle, with strange abbreviations etc. I might make an exception and
go up to 75-76, and hope that nobody notices :) So, in that range,
limiting ourselves to 70 chars would be catastrophic.

Thanks!
Laszlo


  reply	other threads:[~2018-03-02 10:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01  6:57 [PATCH v5 0/6] Add translation support to generic PciHostBridge Heyi Guo
2018-03-01  6:57 ` [PATCH v5 1/6] CorebootPayloadPkg/PciHostBridgeLib: Init PCI aperture to 0 Heyi Guo
2018-03-14 11:24   ` Ard Biesheuvel
2018-03-01  6:57 ` [PATCH v5 2/6] OvmfPkg/PciHostBridgeLib: " Heyi Guo
2018-03-01 10:17   ` Laszlo Ersek
2018-03-01 10:48     ` Guo Heyi
2018-03-02 10:19       ` Laszlo Ersek
2018-03-05  8:23         ` Guo Heyi
2018-03-01 10:20   ` Laszlo Ersek
2018-03-01 10:25     ` Guo Heyi
2018-03-01 12:03     ` Ni, Ruiyu
2018-03-02 10:08       ` Laszlo Ersek [this message]
2018-03-01  6:57 ` [PATCH v5 3/6] MdeModulePkg/PciHostBridgeLib.h: add address Translation Heyi Guo
2018-03-01  6:57 ` [PATCH v5 4/6] MdeModulePkg/PciHostBridgeDxe: Add support for address translation Heyi Guo
2018-03-06  2:44   ` Guo Heyi
2018-03-07  4:30     ` Ni, Ruiyu
2018-03-07  6:01       ` Guo Heyi
2018-03-14  7:57         ` Ni, Ruiyu
2018-03-14 11:25           ` Ard Biesheuvel
2018-03-15  2:57           ` Guo Heyi
2018-03-15  3:25             ` Ni, Ruiyu
2018-03-12 17:18       ` Ard Biesheuvel
2018-03-13  3:00         ` Ni, Ruiyu
2018-03-13  7:31           ` Guo Heyi
2018-03-13  8:04             ` Ard Biesheuvel
2018-03-01  6:57 ` [PATCH v5 5/6] MdeModulePkg/PciBus: convert host address to device address Heyi Guo
2018-03-01  6:57 ` [PATCH v5 6/6] MdeModulePkg/PciBus: return CPU address for GetBarAttributes Heyi Guo
2018-03-01  8:28 ` [PATCH v5 0/6] Add translation support to generic PciHostBridge Ard Biesheuvel
2018-03-15  1:07 ` Ni, Ruiyu

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-list 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=5fdaa2e0-442c-04cd-e362-659abce87438@redhat.com \
    --to=devel@edk2.groups.io \
    /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