[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180709094535.pmknb3pf7uq3xxua@pathway.suse.cz>
Date: Mon, 9 Jul 2018 11:45:35 +0200
From: Petr Mladek <pmladek@...e.com>
To: Theodore Ts'o <tytso@....edu>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"Tobin C. Harding" <me@...in.cc>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vsprintf: fix build warning
On Fri 2018-07-06 11:49:51, Steven Rostedt wrote:
> On Fri, 6 Jul 2018 23:42:13 +0900
> Sergey Senozhatsky <sergey.senozhatsky@...il.com> wrote:
>
> > On (07/06/18 15:47), Arnd Bergmann wrote:
> > [..]
> > > Fixes: bfe80ed3d7c7 ("vsprintf: add command line option debug_boot_weak_hash")
> >
> > Seems like this one is still in linux-next.
> > Can we squash this patch and bfe80ed3d7c7?
> >
>
> I prefer not to do squashes unless absolutely necessary. Yes, it is in
> next, but even branches pulled into next should try to resist rebasing
> (I never rebase my next branch unless there is a real bug that will
> break bisecting).
>
> As this is just a warning fix, and not something that should break any
> bisect, I say keep it separate. Rebases tend to cause issues.
Ted, just to be sure, are you going to take it via the random tree,
please?
Best Regards,
Petr
Powered by blists - more mailing lists