From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-firmware@kernel.org,
Bingbu Cao <bingbu.cao@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [GIT PULL] Intel Image Processing Unit 2 firmware
Date: Thu, 29 Feb 2024 17:50:11 +0200 [thread overview]
Message-ID: <ZeCnszfWGrj7HpPu@smile.fi.intel.com> (raw)
In-Reply-To: <ZeCGEN8PgbkY3k_g@kekkonen.localdomain>
On Thu, Feb 29, 2024 at 01:26:40PM +0000, Sakari Ailus wrote:
> Hi folks,
>
> This PR adds firmware files for Intel IPU2. The atomisp driver that needs
> the firmware is currently in staging.
>
>
> The following changes since commit fe0274513384acb3be3756ae17da97f551a1e0e7:
>
> Merge branch 'robot/patch-0-1709160821' into 'main' (2024-02-28 23:13:23 +0000)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/sailus/linux-firmware.git tags/ipu2-2024-02-29-2
>
> for you to fetch changes up to 28fbeb4f8b8cf5fa214eeaa93c83d4ee779d7a5b:
>
> Intel IPU2: Add firmware files (2024-02-29 15:24:23 +0200)
>
> ----------------------------------------------------------------
> IPU2 firmware binaries
>
> ----------------------------------------------------------------
> Sakari Ailus (1):
> Intel IPU2: Add firmware files
Whatever I commented on, please pull this. We have tons of users who will
benefit of this firmware to be supplied via linux-firmware rather harvesting
it somewhere else.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-02-29 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 13:26 [GIT PULL] Intel Image Processing Unit 2 firmware Sakari Ailus
2024-02-29 14:08 ` Andy Shevchenko
2024-02-29 14:13 ` Andy Shevchenko
2024-02-29 14:17 ` Hans de Goede
2024-02-29 14:41 ` Andy Shevchenko
2024-02-29 14:47 ` Hans de Goede
2024-02-29 16:17 ` Andy Shevchenko
2024-02-29 15:50 ` Andy Shevchenko [this message]
2024-03-01 19:19 ` Josh Boyer
2024-03-04 8:06 ` Sakari Ailus
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=ZeCnszfWGrj7HpPu@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-firmware@kernel.org \
--cc=sakari.ailus@linux.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 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.