public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firmware: stratix10-svc: update for v6.14
Date: Sun, 5 Jan 2025 20:27:59 -0600	[thread overview]
Message-ID: <8435d13a-0bc0-43a4-b5a4-1497bf0ec3c7@kernel.org> (raw)
In-Reply-To: <2025010332-hurry-regular-535a@gregkh>

On 1/3/25 00:25, Greg KH wrote:
> On Thu, Jan 02, 2025 at 08:20:03PM -0600, Dinh Nguyen wrote:
>> The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
>>
>>    Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
>>
>> are available in the Git repository at:
>>
>>    git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_firmware_update_for_v6.14
>>
>> for you to fetch changes up to d31679f42e19780b4564cd1c5f90c1f3249f00c7:
>>
>>    firmware: stratix10-svc: Use kthread_run_on_cpu() (2024-12-16 18:30:11 -0600)
>>
>> ----------------------------------------------------------------
>> SoCFPGA Firmware update for v6.14
>> - Use kthread_run_on_cpu()
>>
>> ----------------------------------------------------------------
>> Frederic Weisbecker (1):
>>        firmware: stratix10-svc: Use kthread_run_on_cpu()
>>
>>   drivers/firmware/stratix10-svc.c | 9 +++------
>>   1 file changed, 3 insertions(+), 6 deletions(-)
> 
> You sent this twice on purpose, did something change?
> 

Apologies, not sure what happened. Nothing changed, please just take the 
first one.

Thanks,
Dinh


  reply	other threads:[~2025-01-06  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  2:20 [GIT PULL] firmware: stratix10-svc: update for v6.14 Dinh Nguyen
2025-01-03  2:20 ` Dinh Nguyen
2025-01-03  6:25   ` Greg KH
2025-01-06  2:27     ` Dinh Nguyen [this message]
2025-01-09  9:56   ` Greg KH

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=8435d13a-0bc0-43a4-b5a4-1497bf0ec3c7@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox