[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190612231535.253a8a20@canb.auug.org.au>
Date: Wed, 12 Jun 2019 23:15:35 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@...radead.org>
Cc: Wolfram Sang <wsa@...-dreams.de>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ruslan Babayev <ruslan@...ayev.com>,
Andrew de Quincey <adq_dvb@...skialf.net>
Subject: Re: linux-next: build warning after merge of the i2c tree
Hi all,
On Wed, 12 Jun 2019 09:32:29 -0300 Mauro Carvalho Chehab <mchehab@...radead.org> wrote:
>
> Em Wed, 12 Jun 2019 14:04:39 +0200
> Wolfram Sang <wsa@...-dreams.de> escreveu:
>
> > > > OK, so that means I should send my pull request after yours in the next
> > > > merge window? To avoid the build breakage?
> > >
> > > Either that or you can apply my patch on your tree before the
> > > patch that caused the breakage.
> > >
> > > Just let me know what works best for you.
> >
> > Hmm, the offending patch is already in -next and I don't rebase my tree.
> > So, I guess it's the merge window dependency then.
> >
> Ok, I'll merge it through my tree then.
It should go into the i2c tree (since that is where the *warning* was
introduced). It is only a warning and there won't be many patches
between the patch that introduced the warning and this one that fixes
it. This patch could then have a Fixes tag that makes sense i.e. it
will reference a previous commit.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists