All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Marek Behún" <kabel@kernel.org>
Cc: linux-pci@vger.kernel.org, "Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH v2 0/2] PCI: aardvark controller changes BATCH 5 (subset)
Date: Mon, 13 Jun 2022 18:43:00 -0500	[thread overview]
Message-ID: <20220613234300.GA726841@bhelgaas> (raw)
In-Reply-To: <20220524132827.8837-1-kabel@kernel.org>

On Tue, May 24, 2022 at 03:28:25PM +0200, Marek Behún wrote:
> Hello Bjorn,
> 
> since Lorenzo is AFK but gave his review for patches 3 and 5 of fifth
> batch of Aardvark changes, and you only requested to use FIELD_PREP [1]
> in order to avoid adding new _SHIFT macros, I am now sending these two
> patches to you. Could we get this merged?
> 
> Thanks.
> 
> Marek
> 
> Changes since v1:
> - dropped all patches but 3 and 5
> - changed patch 5 to use FIELD_PREP instead of _SHIFT macro
> 
> [1] https://lore.kernel.org/linux-arm-kernel/20220518202729.GA4606@bhelgaas/
> 
> Pali Rohár (2):
>   PCI: aardvark: Add support for AER registers on emulated bridge
>   PCI: aardvark: Fix reporting Slot capabilities on emulated bridge
> 
>  drivers/pci/controller/pci-aardvark.c | 110 +++++++++++++++++++++++---
>  1 file changed, 101 insertions(+), 9 deletions(-)

Applied to pci/ctrl/aardvark for v5.20, thanks!

      parent reply	other threads:[~2022-06-13 23:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 13:28 [PATCH v2 0/2] PCI: aardvark controller changes BATCH 5 (subset) Marek Behún
2022-05-24 13:28 ` [PATCH v2 1/2] PCI: aardvark: Add support for AER registers on emulated bridge Marek Behún
2022-05-26 20:38   ` Rob Herring
2022-05-29 10:08     ` Marek Behún
2022-05-31 19:55       ` Rob Herring
2022-05-24 13:28 ` [PATCH v2 2/2] PCI: aardvark: Fix reporting Slot capabilities " Marek Behún
2022-06-13 23:43 ` 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=20220613234300.GA726841@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=kabel@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pali@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.