[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170828151719.GA28115@kroah.com>
Date: Mon, 28 Aug 2017 17:17:20 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Marcus Wolf <marcus.wolf@...f-entwicklungen.de>
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: Send a large patch right now or is it better to do it later?
On Fri, Jul 28, 2017 at 05:16:56PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> according to the proposals of Walter Harms, I revised the rf69.c: I replaced
> some macros with inline functions and removed some obsolete ifdefs. According to
> walter this will improve the resource situation. In addition the readybility is
> enhanced, since lines got shorter. It's a quite big change, that touched nearly
> every function in that file.
> I was testing the new code for a while now and did not observer a problem so
> far. But I don't have a kind of unit test, so my tests for sure didn't cover
> everything.
>
> Is it a good time, to submit such a change in these days, or is it prefrable to
> submit it later?
> In adition, I am a bit afraid of my current mailtool doing something
> unexpected...
You can send patches anytime, don't worry about timing, I can handle
putting them in the correct patch queue.
> P.S. Can you process diffs fom SVN, too, or is it mandatory to create the diff
> with git?
As long as it is in normal patch format, I can apply it. Personally, I
use quilt to generate patche, which uses 'diff', and that works just
fine.
thanks,
greg k-h
Powered by blists - more mailing lists