From: Mario Limonciello <superm1@gmail.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Josh Boyer <jwboyer@kernel.org>,
linux-firmware@kernel.org, netdev@vger.kernel.org,
przemyslaw.kitszel@intel.com
Subject: Re: [linux-firmware v1 0/3][pull request] Intel Wired LAN Firmware Updates 2023-11-22
Date: Mon, 27 Nov 2023 13:14:52 -0600 [thread overview]
Message-ID: <CA+EcB1OSrgy8Ni0Y2cd-5xfr9FHQJ2-RK3umwVwDoQYf2A3stQ@mail.gmail.com> (raw)
In-Reply-To: <e77ba51d-2bd9-ed70-ec9c-60799fa21053@intel.com>
On Mon, Nov 27, 2023 at 11:21 AM Tony Nguyen <anthony.l.nguyen@intel.com> wrote:
>
> On 11/27/2023 6:06 AM, Josh Boyer wrote:
> > On Wed, Nov 22, 2023 at 7:10 PM Josh Boyer <jwboyer@kernel.org> wrote:
> >>
> >> On Wed, Nov 22, 2023 at 12:30 PM Tony Nguyen <anthony.l.nguyen@intel.com> wrote:
> >>>
> >>> Update the various ice DDP packages to the latest versions.
> >>>
> >>> Thanks,
> >>> Tony
> >>>
> >>> The following changes since commit 9552083a783e5e48b90de674d4e3bf23bb855ab0:
> >>>
> >>> Merge branch 'robot/pr-0-1700470117' into 'main' (2023-11-20 13:09:23 +0000)
> >>>
> >>> are available in the Git repository at:
> >>>
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/firmware.git dev-queue
> >>>
> >>> for you to fetch changes up to c71fdbc575b79eff31db4ea243f98d5f648f7f0f:
> >>>
> >>> ice: update ice DDP wireless_edge package to 1.3.13.0 (2023-11-22 09:14:39 -0800)
> >>>
> >>> ----------------------------------------------------------------
> >>> Przemek Kitszel (3):
> >>> ice: update ice DDP package to 1.3.35.0
> >>> ice: update ice DDP comms package to 1.3.45.0
> >>> ice: update ice DDP wireless_edge package to 1.3.13.0
> >>
> >> Sending a pull request and all of the patches to the list individually
> >> seems to have confused the automation we have to grab stuff from the
> >> list. The first two patches are merged and pushed out:
> >>
> >> https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/75
> >> https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/76
> >>
> >> but we never got an auto-MR for patch #3, and the pull request MR now
> >> conflicts because we applied the first two patches in the series from
> >> the individual patches.
> >>
> >> https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/74
> >>
> >> Mario or I can fix this up, but in the future it'll just be easier if
> >> you send either a pull request or individual patches, not both.
> >
> > The third patch is now merged and pushed out.
> >
> > https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/85
>
> Thanks Josh. I was out for the Thanksgiving holiday. Will send one or
> the other on future sends.
>
> - Tony
Even better - if you can open up MR directly at
https://gitlab.com/kernel-firmware/linux-firmware we don't need to worry
about the robot messing up or you needing to pull one back because of
a mistake etc.
Win win for everyone.
prev parent reply other threads:[~2023-11-27 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 17:30 [linux-firmware v1 0/3][pull request] Intel Wired LAN Firmware Updates 2023-11-22 Tony Nguyen
2023-11-22 17:30 ` [linux-firmware v1 1/3] ice: update ice DDP package to 1.3.35.0 Tony Nguyen
2023-11-22 17:30 ` [linux-firmware v1 2/3] ice: update ice DDP comms package to 1.3.45.0 Tony Nguyen
2023-11-22 17:30 ` [linux-firmware v1 3/3] ice: update ice DDP wireless_edge package to 1.3.13.0 Tony Nguyen
2023-11-23 0:10 ` [linux-firmware v1 0/3][pull request] Intel Wired LAN Firmware Updates 2023-11-22 Josh Boyer
2023-11-27 14:06 ` Josh Boyer
2023-11-27 17:21 ` Tony Nguyen
2023-11-27 19:14 ` Mario Limonciello [this message]
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=CA+EcB1OSrgy8Ni0Y2cd-5xfr9FHQJ2-RK3umwVwDoQYf2A3stQ@mail.gmail.com \
--to=superm1@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).