public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "David Woodhouse" <dwmw2@infradead.org>
To: devel@edk2.groups.io, lersek@redhat.com, jljusten@gmail.com,
	afish@apple.com,  Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [edk2-devel] [PATCH 1/2] LegacyBios: set NumberBbsEntries to the size of BbsTable
Date: Mon, 24 Jun 2019 12:48:43 +0100	[thread overview]
Message-ID: <06f6c0ecaa5214b901cadc244ec62ab53203871d.camel@infradead.org> (raw)
In-Reply-To: <3f9de0c1-afc3-1984-fe1c-4ea4021974ba@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]

On Thu, 2019-06-20 at 22:35 +0200, Laszlo Ersek wrote:
> My past mistake doesn't excuse the current commit message ;)
> 
> Anyway, I intentionally didn't ask for just repeating the commit msg
> title in the commit msg body. You could mention why the pre-patch
> expression (1 + 2 * MAX_IDE_CONTROLLER) is wrong, or wasteful. It's not
> obvious at all from just the patch itself (without looking at the larger
> context in the source file). You can save time for reviewers by giving
> hints in the commit message. And if you *can* save time for reviewers,
> you should. :)

With specific requests for things that weren't already in the subject
line, I'm perfectly happy to add more.

Better now?

> > > I think your note on patch#2 is valuable too and should be captured in
> > > the commit message body. Please consider formulating it with a bit more
> > > neutral tone :)
> > 
> > I would prefer to express that particular concern in 'diff -up' form
> > when actually fixing it :)
> > 
> 
> I'm a big fan of detailed commit messages. It's OK (and welcome) to
> describe current shortcomings even if you intend to fix them later.
> 
> The commit message could also capture in one or two sentences what the
> patch does (locate handles with BlockIo instances, filter out some of
> them based on their DevicePath instances and other criteria, then for
> each handle, take the PCI B/D/F from the most specific PciIo instance on
> the device path). Anyway, I wouldn't like to obsess about this.

Done.

> series
> Acked-by: Laszlo Ersek <lersek@redhat.com>

Out of interest, why Acked-by: for these two vs. Reviewed-by: for the
first one? It's all under OvmfPkg now (which is made clearer in the
series I posted on Friday than it is in the subject line here).

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]

  parent reply	other threads:[~2019-06-24 11:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1359122038.24865.19.camel@shinybook.infradead.org>
     [not found] ` <1359147866-15605-3-git-send-email-lersek@redhat.com>
2019-06-18  9:13   ` [PATCH 2/2] LegacyBbs: add boot entries for virtio-blk devices David Woodhouse
2019-06-19 12:44     ` [PATCH 1/2] LegacyBios: set NumberBbsEntries to the size of BbsTable David Woodhouse
2019-06-20 16:12       ` [edk2-devel] " Laszlo Ersek
2019-06-20 17:32         ` David Woodhouse
2019-06-20 20:35           ` Laszlo Ersek
2019-06-21 10:59             ` David Woodhouse
2019-06-24 22:08               ` Laszlo Ersek
2019-06-24 22:22                 ` Laszlo Ersek
     [not found]                   ` <F95F0A95-4638-4B08-BDAF-53A797A6B877@infradead.org>
2019-06-25  7:06                     ` Ni, Ray
2019-06-25 10:34                       ` Laszlo Ersek
2019-06-25  7:29                 ` David Woodhouse
2019-06-24 11:48             ` David Woodhouse [this message]
2019-06-24 21:49               ` Laszlo Ersek
2019-06-19 12:44     ` [PATCH 2/2] LegacyBbs: Add boot entries for VirtIO and NVME devices David Woodhouse

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=06f6c0ecaa5214b901cadc244ec62ab53203871d.camel@infradead.org \
    --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