Message ID | CALdTtnueGPXkR3KNoTGHugCD4A0=COv43Pv_hxzPfUU6PAiPfg@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Wed, Mar 08, 2017 at 12:59:59PM -0700, dann frazier wrote: > Here's a set of miscellaneous arm64 changes for zesty. It includes > fixes (erratum/quirking) for the QDF2400 platform, a follow-up fix for > the previously merged VFIO backport, and a GICv3 ITS performance fix. These patches all need buglinks, otherwise they look fine.
On Wed, Mar 8, 2017 at 2:37 PM, Seth Forshee <seth.forshee@canonical.com> wrote: > On Wed, Mar 08, 2017 at 12:59:59PM -0700, dann frazier wrote: >> Here's a set of miscellaneous arm64 changes for zesty. It includes >> fixes (erratum/quirking) for the QDF2400 platform, a follow-up fix for >> the previously merged VFIO backport, and a GICv3 ITS performance fix. > > These patches all need buglinks, otherwise they look fine. Ah, OK. I'll file bugs and resubmit. Also, I should probably know this by now, but at what stage in the release does the buglink requirement set in? I think historically I've used lazy discovery by submitted cherry-picks w/o buglinks until I get an e-mail like this one, then transition to buglink mode for the rest of the cycle :)
On Wed, Mar 08, 2017 at 03:04:06PM -0700, dann frazier wrote: > On Wed, Mar 8, 2017 at 2:37 PM, Seth Forshee <seth.forshee@canonical.com> wrote: > > On Wed, Mar 08, 2017 at 12:59:59PM -0700, dann frazier wrote: > >> Here's a set of miscellaneous arm64 changes for zesty. It includes > >> fixes (erratum/quirking) for the QDF2400 platform, a follow-up fix for > >> the previously merged VFIO backport, and a GICv3 ITS performance fix. > > > > These patches all need buglinks, otherwise they look fine. > > Ah, OK. I'll file bugs and resubmit. Also, I should probably know this > by now, but at what stage in the release does the buglink requirement > set in? I think historically I've used lazy discovery by submitted > cherry-picks w/o buglinks until I get an e-mail like this one, then > transition to buglink mode for the rest of the cycle :) You should have buglinks for everything after feature freeze. There's no reason you can't include them before then though ;-)