All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Brian Norris <briannorris@chromium.org>,
	Julius Werner <jwerner@chromium.org>,
	chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register()
Date: Wed, 24 Apr 2024 16:43:00 +0800	[thread overview]
Message-ID: <ZijGFJbqRlKykG8E@google.com> (raw)
In-Reply-To: <9fbf48a6-239b-4304-850d-6ca43af93a71@linaro.org>

On Wed, Apr 24, 2024 at 08:40:34AM +0200, Krzysztof Kozlowski wrote:
> On 30/03/2024 20:49, Krzysztof Kozlowski wrote:
> > Moving the .owner setting code to the core this effectively fixes
> > missing .owner in framebuffer-coreboot, memconsole-coreboot and vpd
> > drivers.
> > 
> 
> It has been almost a month. Any comments on this patchset?

They have been applied for a while, thanks!  Just realized this email was
forgotten.

[1/2] firmware: coreboot: store owner from modules with coreboot_driver_register()
      commit: 46c6685e7e886b7fa098465f8bfd139a253365e4
[2/2] firmware: google: cbmem: drop driver owner initialization
      commit: 7f20f21c22aa22e488530f66bf4fc168e427f5bd

  reply	other threads:[~2024-04-24  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 19:49 [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register() Krzysztof Kozlowski
2024-03-30 19:49 ` [PATCH 1/2] " Krzysztof Kozlowski
2024-03-30 19:49 ` [PATCH 2/2] firmware: google: cbmem: drop driver owner initialization Krzysztof Kozlowski
2024-04-24  6:40 ` [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register() Krzysztof Kozlowski
2024-04-24  8:43   ` Tzung-Bi Shih [this message]
2024-05-27  2:55 ` patchwork-bot+chrome-platform
2024-05-27  3:07 ` patchwork-bot+chrome-platform

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=ZijGFJbqRlKykG8E@google.com \
    --to=tzungbi@kernel.org \
    --cc=briannorris@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=jwerner@chromium.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.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.