From: Michal Marek <mmarek@suse.cz>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Greg KH <gregkh@linux-foundation.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] Makefile: Build with -Werror=date-time if the compiler supports it
Date: Mon, 27 Jan 2014 23:57:32 +0100 [thread overview]
Message-ID: <52E6E45C.1010805@suse.cz> (raw)
In-Reply-To: <20140114214614.GA26965@kroah.com>
On 14.1.2014 22:46, Greg KH wrote:
> On Tue, Jan 14, 2014 at 01:40:15PM -0800, Josh Triplett wrote:
>> On Tue, Jan 14, 2014 at 09:56:53PM +0100, Michal Marek wrote:
>>> Dne 3.1.2014 22:00, Josh Triplett napsal(a):
>>>> On Fri, Jan 03, 2014 at 09:55:16PM +0100, Michal Marek wrote:
>>>>> On 3.1.2014 21:29, Josh Triplett wrote:
>>>>>> Please feel free to take the entire series through your tree; I received
>>>>>> some maintainer acks, but no indications that the patches are going
>>>>>> through their trees.
>>>>>
>>>>> OK. I will wait until mid next week and commit with any acks received.
>>>>
>>>> Thanks!
>>>
>>> I did not find time last week and Greg was faster and merged the driver
>>> patches. But I'm reluctant to only merge the Makefile patch now, because
>>> the kbuild branch would not build. I think I will send the patch to
>>> Linus after 3.14-rc1.
>>
>> Greg, if you already have all the driver patches in your tree, perhaps
>> you could go ahead and take the Makefile patch through your tree as
>> well? (Assuming that's OK with you, Michal?)
>
> Did I really grab all of the other patches? I don't remember how many
> there were in this series for stuff I maintain. If I have them all,
> sure, I'll be glad to take it, otherwise I agree with Michal, it should
> be sent to Linus after 3.14-rc1 is out to make sure everything is
> properly synced up and you didn't miss any new drivers coming in that
> missed getting converted.
FYI: The remaining patches are now in the kbuild.git#drop-time branch
and also in the for-next branch.
Thanks,
Michal
prev parent reply other threads:[~2014-01-27 22:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 21:54 [PATCH 0/7] Eliminate uses of __DATE__ and __TIME__ Josh Triplett
2013-12-23 21:54 ` [PATCH 1/7] mtd: denali: Drop print of build date/time Josh Triplett
2013-12-26 8:24 ` Jingoo Han
2013-12-26 8:24 ` Jingoo Han
2014-01-09 16:55 ` Brian Norris
2014-01-09 16:55 ` Brian Norris
2013-12-23 21:55 ` [PATCH 2/7] net: wireless: brcm80211: Drop debug version with " Josh Triplett
2013-12-23 21:55 ` [PATCH 3/7] staging: rtl8188eu: Drop print of " Josh Triplett
2013-12-24 1:15 ` Larry Finger
2013-12-23 21:55 ` [PATCH 4/7] staging: rts5139: Drop print of build time Josh Triplett
2013-12-23 21:55 ` [PATCH 5/7] staging: wlags49_h2: Drop debug macro recording build date/time Josh Triplett
2013-12-23 21:55 ` [PATCH 6/7] x86: math-emu: Drop already-disabled print of build date Josh Triplett
2013-12-23 21:56 ` [PATCH 7/7] Makefile: Build with -Werror=date-time if the compiler supports it Josh Triplett
2014-01-03 16:40 ` Michal Marek
2014-01-03 20:29 ` Josh Triplett
2014-01-03 20:55 ` Michal Marek
2014-01-03 21:00 ` Josh Triplett
2014-01-14 20:56 ` Michal Marek
2014-01-14 21:40 ` Josh Triplett
2014-01-14 21:46 ` Greg KH
2014-01-27 22:57 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E6E45C.1010805@suse.cz \
--to=mmarek@suse.cz \
--cc=gregkh@linux-foundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.