Message ID | 1533309679-20903-1-git-send-email-dinguyen@kernel.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT/RFC,PULL,LTSI-4.14] SoCFPGA, NIOS2 SoCs and Drivers to v4.18 | expand |
Hi Dinh, On Fri, Aug 3, 2018 at 5:21 PM Dinh Nguyen <dinguyen@kernel.org> wrote: > In preparation for the v4.14-ltsi release, I'd like to have these backported > patches be considered for the release. Thanks for your backport! > The following changes since commit 53208e12faa5b8c6eac4eb1d23d6e3fae450fc5a: > > Linux 4.14.59 (2018-07-28 07:55:45 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_for_v4.14_ltsi > > for you to fetch changes up to b894b5008949db0457dcda436291c70d74f04512: > > reset: socfpga: build the reset-socfpga for Stratix10 SOC (2018-08-03 09:11:49 -0500) > > ---------------------------------------------------------------- > LTSI-v4.14 Preparation for SoCFPGA SoCs (v4.18) > > Base: > * v4.14.59 > > Backports of the following components to v4.18 > > * Stratix10 enablement(clock driver) > * NIOS2 updates > * FPGA manager updates All of the above looks fairly low-risk and self-contained to me. I can confirm all backported commits are present either in v4.18-rc8, or (in some form) in current linux-next. Note that when backporting, it is a good idea to record the original upstream commit ID in the patch description, either by manually adding commit <sha1> upstream like Greg does, or by letting "git cherry-pick" automatically add (cherry picked from commit <sha1>) using the "-x" option, like Simon Horman does. Doing so would have saved me some (scripted) git patch-id matching ;-) Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Hi Geert, On 08/08/2018 10:57 AM, Geert Uytterhoeven wrote: > Hi Dinh, > > On Fri, Aug 3, 2018 at 5:21 PM Dinh Nguyen <dinguyen@kernel.org> wrote: >> In preparation for the v4.14-ltsi release, I'd like to have these backported >> patches be considered for the release. > > Thanks for your backport! > >> The following changes since commit 53208e12faa5b8c6eac4eb1d23d6e3fae450fc5a: >> >> Linux 4.14.59 (2018-07-28 07:55:45 +0200) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_for_v4.14_ltsi >> >> for you to fetch changes up to b894b5008949db0457dcda436291c70d74f04512: >> >> reset: socfpga: build the reset-socfpga for Stratix10 SOC (2018-08-03 09:11:49 -0500) >> >> ---------------------------------------------------------------- >> LTSI-v4.14 Preparation for SoCFPGA SoCs (v4.18) >> >> Base: >> * v4.14.59 >> >> Backports of the following components to v4.18 >> >> * Stratix10 enablement(clock driver) >> * NIOS2 updates >> * FPGA manager updates > > All of the above looks fairly low-risk and self-contained to me. > > I can confirm all backported commits are present either in v4.18-rc8, or > (in some form) in current linux-next. > > Note that when backporting, it is a good idea to record the original > upstream commit ID in the patch description, either by manually adding > > commit <sha1> upstream > > like Greg does, or by letting "git cherry-pick" automatically add > > (cherry picked from commit <sha1>) > > using the "-x" option, like Simon Horman does. > Doing so would have saved me some (scripted) git patch-id matching ;-) > Thanks for the tip. Do you need me to respin another branch with this information? Thanks, Dinh
Hi Dinh, On Mon, Aug 13, 2018 at 3:36 PM Dinh Nguyen <dinguyen@kernel.org> wrote: > On 08/08/2018 10:57 AM, Geert Uytterhoeven wrote: > > On Fri, Aug 3, 2018 at 5:21 PM Dinh Nguyen <dinguyen@kernel.org> wrote: > >> In preparation for the v4.14-ltsi release, I'd like to have these backported > >> patches be considered for the release. > > > > Thanks for your backport! > > > >> The following changes since commit 53208e12faa5b8c6eac4eb1d23d6e3fae450fc5a: > >> > >> Linux 4.14.59 (2018-07-28 07:55:45 +0200) > >> > >> are available in the git repository at: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_for_v4.14_ltsi > >> > >> for you to fetch changes up to b894b5008949db0457dcda436291c70d74f04512: > >> > >> reset: socfpga: build the reset-socfpga for Stratix10 SOC (2018-08-03 09:11:49 -0500) > >> > >> ---------------------------------------------------------------- > >> LTSI-v4.14 Preparation for SoCFPGA SoCs (v4.18) > >> > >> Base: > >> * v4.14.59 > >> > >> Backports of the following components to v4.18 > >> > >> * Stratix10 enablement(clock driver) > >> * NIOS2 updates > >> * FPGA manager updates > > > > All of the above looks fairly low-risk and self-contained to me. > > > > I can confirm all backported commits are present either in v4.18-rc8, or > > (in some form) in current linux-next. > > > > Note that when backporting, it is a good idea to record the original > > upstream commit ID in the patch description, either by manually adding > > > > commit <sha1> upstream > > > > like Greg does, or by letting "git cherry-pick" automatically add > > > > (cherry picked from commit <sha1>) > > > > using the "-x" option, like Simon Horman does. > > Doing so would have saved me some (scripted) git patch-id matching ;-) > > > > Thanks for the tip. Do you need me to respin another branch with this > information? Personally, I think more traceability never hurts, so a respin would be nice. However, I would like to defer the final decision to Greg. Gr{oetje,eeting}s, Geert
On Tue, Aug 21, 2018 at 07:51:45PM +0200, Geert Uytterhoeven wrote: > Hi Dinh, > > On Mon, Aug 13, 2018 at 3:36 PM Dinh Nguyen <dinguyen@kernel.org> wrote: > > On 08/08/2018 10:57 AM, Geert Uytterhoeven wrote: > > > On Fri, Aug 3, 2018 at 5:21 PM Dinh Nguyen <dinguyen@kernel.org> wrote: > > >> In preparation for the v4.14-ltsi release, I'd like to have these backported > > >> patches be considered for the release. > > > > > > Thanks for your backport! > > > > > >> The following changes since commit 53208e12faa5b8c6eac4eb1d23d6e3fae450fc5a: > > >> > > >> Linux 4.14.59 (2018-07-28 07:55:45 +0200) > > >> > > >> are available in the git repository at: > > >> > > >> git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_for_v4.14_ltsi > > >> > > >> for you to fetch changes up to b894b5008949db0457dcda436291c70d74f04512: > > >> > > >> reset: socfpga: build the reset-socfpga for Stratix10 SOC (2018-08-03 09:11:49 -0500) > > >> > > >> ---------------------------------------------------------------- > > >> LTSI-v4.14 Preparation for SoCFPGA SoCs (v4.18) > > >> > > >> Base: > > >> * v4.14.59 > > >> > > >> Backports of the following components to v4.18 > > >> > > >> * Stratix10 enablement(clock driver) > > >> * NIOS2 updates > > >> * FPGA manager updates > > > > > > All of the above looks fairly low-risk and self-contained to me. > > > > > > I can confirm all backported commits are present either in v4.18-rc8, or > > > (in some form) in current linux-next. > > > > > > Note that when backporting, it is a good idea to record the original > > > upstream commit ID in the patch description, either by manually adding > > > > > > commit <sha1> upstream > > > > > > like Greg does, or by letting "git cherry-pick" automatically add > > > > > > (cherry picked from commit <sha1>) > > > > > > using the "-x" option, like Simon Horman does. > > > Doing so would have saved me some (scripted) git patch-id matching ;-) > > > > > > > Thanks for the tip. Do you need me to respin another branch with this > > information? > > Personally, I think more traceability never hurts, so a respin would be nice. > However, I would like to defer the final decision to Greg. Yes, a respin with this required information is essential. Dinh, please do so, thanks! greg k-h