From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/3] kconfig: do not special-case 'MODULES' symbol
Date: Wed, 04 Sep 2013 10:22:44 +0200 [thread overview]
Message-ID: <5226EDD4.9090300@suse.cz> (raw)
In-Reply-To: <20130903211237.GA3681@free.fr>
Dne 3.9.2013 23:12, Yann E. MORIN napsal(a):
> Doh... I forgot to send an intro mail first. Seems holidays really were
> a good break! :-)
:-)
> Anyway, this series might be a bit late to go in for 3.12, but it has
> previously been discussed with you and Sam.
>
> If you feel it's too touchy for 3.12, then I believe it can easily wait
> for 3.13.
>
> If you want it for 3.12, I can send a pull-request if that's easier for
> you.
Please send me a pull request regardless, so that the second commit's
changelog references the right commit id. I'll play with this and will
merge it into kbuild.git if there are no problems. It's two days into
the merge window, so no big deal (shh!).
Michal
next prev parent reply other threads:[~2013-09-04 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 21:04 [PATCH 1/3] kconfig: do not special-case 'MODULES' symbol Yann E. MORIN
2013-09-03 21:04 ` [PATCH 2/3] kconfig: regenerate bison parser Yann E. MORIN
2013-09-03 21:04 ` [PATCH 3/3] kconfig: do not allow more than one symbol to have 'option modules' Yann E. MORIN
2013-09-03 21:12 ` [PATCH 1/3] kconfig: do not special-case 'MODULES' symbol Yann E. MORIN
2013-09-04 8:22 ` Michal Marek [this message]
2013-09-05 9:38 ` Michal Marek
2013-09-05 10:02 ` Michal Marek
2013-09-06 9:48 ` Yann E. MORIN
2013-09-06 9:47 ` Yann E. MORIN
2013-09-06 10:02 ` Michal Marek
-- strict thread matches above, loose matches on Subject: below --
2013-09-04 10:59 [pull request] Pull request for branch yem/kconfig-for-next Yann E. MORIN
2013-09-04 10:59 ` [PATCH 1/3] kconfig: do not special-case 'MODULES' symbol Yann E. MORIN
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=5226EDD4.9090300@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=yann.morin.1998@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox