From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
rafael@kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-acpi@vger.kernel.org,
Alexander Graf <graf@amazon.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH 2/3 v6] ACPI: allow longer device IDs
Date: Tue, 1 Mar 2022 16:25:19 +0200 [thread overview]
Message-ID: <Yh4sz8tpNxUecRQw@smile.fi.intel.com> (raw)
In-Reply-To: <e9bfc654-5504-29ff-5a5a-b73f24691600@redhat.com>
On Tue, Mar 01, 2022 at 11:35:12AM +0100, Hans de Goede wrote:
> On 2/28/22 19:33, Jason A. Donenfeld wrote:
> > Co-authored-by: Jason A. Donenfeld <Jason@zx2c4.com>
Official tag is Co-developed-by
> > [Jason: reworked commit message a bit, went with len=16 approach.]
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-01 14:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 22:06 [PATCH v5 0/3] ACPI: VM fork detection for RNG Jason A. Donenfeld
2022-02-26 22:06 ` [PATCH v5 1/3] random: add mechanism for VM forks to reinitialize crng Jason A. Donenfeld
2022-02-26 22:06 ` [PATCH v5 2/3] ACPI: allow longer device IDs Jason A. Donenfeld
2022-02-27 7:31 ` Ard Biesheuvel
2022-02-27 7:37 ` Ard Biesheuvel
2022-02-27 10:03 ` Jason A. Donenfeld
2022-02-27 10:30 ` Ard Biesheuvel
2022-02-27 10:47 ` Ard Biesheuvel
2022-02-27 11:38 ` Alexander Graf
2022-02-27 11:43 ` Ard Biesheuvel
2022-02-27 11:48 ` Alexander Graf
2022-02-27 11:59 ` Ard Biesheuvel
2022-02-27 11:42 ` Alexander Graf
2022-02-27 12:43 ` Jason A. Donenfeld
2022-02-27 23:27 ` Jason A. Donenfeld
2022-02-28 18:19 ` Rafael J. Wysocki
2022-02-28 18:21 ` Jason A. Donenfeld
2022-02-28 18:33 ` [PATCH 2/3 v6] " Jason A. Donenfeld
2022-02-28 20:46 ` Andy Shevchenko
2022-02-28 20:58 ` Jason A. Donenfeld
2022-02-28 21:02 ` Ard Biesheuvel
2022-02-28 21:27 ` Andy Shevchenko
2022-02-28 21:54 ` Jason A. Donenfeld
2022-02-28 22:14 ` Michael Kelley (LINUX)
2022-02-28 22:17 ` Jason A. Donenfeld
2022-02-28 22:21 ` Ard Biesheuvel
2022-02-28 22:38 ` Michael Kelley (LINUX)
2022-02-28 22:46 ` Ard Biesheuvel
2022-03-22 19:58 ` Michael Kelley (LINUX)
2022-03-22 20:11 ` Jason A. Donenfeld
2022-03-24 19:25 ` Michael Kelley (LINUX)
2022-03-22 22:06 ` Ard Biesheuvel
2022-03-24 19:24 ` Michael Kelley (LINUX)
2022-03-24 19:45 ` Jason A. Donenfeld
2022-03-24 20:14 ` Michael Kelley (LINUX)
2022-03-01 13:12 ` Andy Shevchenko
2022-02-28 22:00 ` Alexander Graf
2022-02-28 22:17 ` Ard Biesheuvel
2022-03-01 10:35 ` Hans de Goede
2022-03-01 10:38 ` Jason A. Donenfeld
2022-03-01 10:49 ` Hans de Goede
2022-03-01 14:25 ` Andy Shevchenko [this message]
2022-03-01 14:48 ` Jason A. Donenfeld
2022-03-01 12:29 ` Rafael J. Wysocki
2022-03-01 10:31 ` [PATCH v5 2/3] " Hans de Goede
2022-02-26 22:06 ` [PATCH v5 3/3] virt: vmgenid: introduce driver for reinitializing RNG on VM fork Jason A. Donenfeld
2022-03-06 16:02 ` Michael Kelley (LINUX)
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=Yh4sz8tpNxUecRQw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@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