[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPdLdqma+YMsZqMB3CD=0UEzBPYf3XoCzjkcCMaOOS2mt+51xQ@mail.gmail.com>
Date: Wed, 20 Nov 2013 10:42:12 -0800
From: Markus Mayer <markus.mayer@...aro.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Wim Van Sebroeck <wim@...ana.be>,
Christian Daudt <bcm@...thebug.org>,
Linaro Patches <patches@...aro.org>,
Matt Porter <matt.porter@...aro.org>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Linux Watchdog List <linux-watchdog@...r.kernel.org>,
ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 1/2] watchdog: bcm281xx: Watchdog Driver
On 20 November 2013 10:40, Guenter Roeck <linux@...ck-us.net> wrote:
> On Wed, Nov 20, 2013 at 10:24:54AM -0800, Markus Mayer wrote:
>> > Hi Markus,
>> >
>> > Yes, I noticed when I merged it into my watchdog-next branch.
>> >
>> > Reminds me ... v3 had a whitespace problem. I don't recall if you fixed
>> > that in v4. If you didn't, that might be a better reason to send v5.
>>
>> That's still there, unfortunately. Trailing space on the first
>> help-text line in Kconfig:
>> Support for the watchdog timer on the following Broadcom BCM281xx
>>
>> So, I'll generate v5 with that fixed. Do you prefer I also rebase it
>> right now to whatever current tip is to take care of the merge
>> conflict?
>>
> I would suggest to wait for -rc1 and rebase to it before you send the new
> version. After all, it won't make it into 3.13 anyway, so no need to hurry.
Sure thing. I'll do that.
Thanks,
-Markus
--
Markus Mayer
Broadcom Landing Team
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists