From: Russ Weight <russell.h.weight@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: <rafael@kernel.org>, <linux-kernel@vger.kernel.org>,
<kbuild-all@lists.01.org>, <trix@redhat.com>,
<lgoncalv@redhat.com>, <yilun.xu@intel.com>, <hao.wu@intel.com>,
<matthew.gerlach@linux.intel.com>,
<basheer.ahmed.muddebihal@intel.com>, <tianfei.zhang@intel.com>
Subject: Re: [PATCH v4 4/8] firmware_loader: Add firmware-upload support
Date: Thu, 21 Apr 2022 10:07:26 -0700 [thread overview]
Message-ID: <dd27add0-fb45-9b99-6ecd-84c4b3b28ef8@intel.com> (raw)
In-Reply-To: <YmGKZtdKqtNg1flU@bombadil.infradead.org>
On 4/21/22 09:46, Luis Chamberlain wrote:
> On Thu, Apr 21, 2022 at 02:32:00PM +0800, kernel test robot wrote:
>> Hi Russ,
> Russ, can you fix this with a new set?
>
> Luis
Yes - I'll take care of it.
- Russ
next prev parent reply other threads:[~2022-04-21 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 23:16 [PATCH v4 0/8] Extend FW framework for user FW uploads Russ Weight
2022-04-19 23:16 ` [PATCH v4 1/8] firmware_loader: Clear data and size in fw_free_paged_buf Russ Weight
2022-04-19 23:16 ` [PATCH v4 2/8] firmware_loader: Check fw_state_is_done in loading_store Russ Weight
2022-04-19 23:16 ` [PATCH v4 3/8] firmware_loader: Split sysfs support from fallback Russ Weight
2022-04-19 23:16 ` [PATCH v4 4/8] firmware_loader: Add firmware-upload support Russ Weight
2022-04-21 6:32 ` kernel test robot
2022-04-21 16:46 ` Luis Chamberlain
2022-04-21 17:07 ` Russ Weight [this message]
2022-04-19 23:16 ` [PATCH v4 5/8] firmware_loader: Add sysfs nodes to monitor fw_upload Russ Weight
2022-04-19 23:16 ` [PATCH v4 6/8] test_firmware: Add test support for firmware upload Russ Weight
2022-04-19 23:16 ` [PATCH v4 7/8] test_firmware: Error injection " Russ Weight
2022-04-19 23:16 ` [PATCH v4 8/8] selftests: firmware: Add firmware upload selftests Russ Weight
2022-04-20 21:37 ` matthew.gerlach
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=dd27add0-fb45-9b99-6ecd-84c4b3b28ef8@intel.com \
--to=russell.h.weight@intel.com \
--cc=basheer.ahmed.muddebihal@intel.com \
--cc=hao.wu@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=tianfei.zhang@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.com \
/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