[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171018160442.kgdwfzobxtcbf636@sirena.co.uk>
Date: Wed, 18 Oct 2017 17:04:42 +0100
From: Mark Brown <broonie@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: Felipe Balbi <balbi@...nel.org>, Tony Lindgren <tony@...mide.com>,
Felipe Balbi <felipe.balbi@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Allen Pais <allen.lkml@...il.com>, linux-omap@...r.kernel.org,
linux-usb@...r.kernel.org,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the usb-gadget tree with the usb tree
On Wed, Oct 18, 2017 at 08:40:04AM -0700, Kees Cook wrote:
> On Wed, Oct 18, 2017 at 7:49 AM, Mark Brown <broonie@...nel.org> wrote:
> > I fixed it up with the USB version and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging. You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
> FWIW, timer_setup() should be preferred over setup_timer().
Bah, that's unfortunate. When more of these come up I'll do that. It
would be better to sort these out in the relevant trees though, there's
quite a few of these conflicts and it's not super obvious if you're not
into the timer code what's preferred.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists