From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Pending kconfig patches
Date: Wed, 31 Aug 2011 13:50:21 +0200 [thread overview]
Message-ID: <4E5E1FFD.9020105@suse.cz> (raw)
In-Reply-To: <CACqU3MUEqL1=s29+ibH3CvVCvm8VDN4RM-8bd+dWxdmeF-d4gw@mail.gmail.com>
On 30.8.2011 02:47, Arnaud Lacombe wrote:
> Hi,
>
> FYI, I've been picking a few patches on the list which have not yet
> reached your kbuild-2.6/kconfig branch. They are available in the git
> repository at:
>
> git://github.com/lacombar/linux-2.6.git kconfig/for-next
>
> and it currently contains:
>
> Arnaud Lacombe (1):
> kconfig: fix __enabled_ macros definition for invisible and
> un-selected symbols
>
> Davidlohr Bueso (1):
> kconfig: handle SIGINT in menuconfig
>
> Lucas De Marchi (1):
> kconfig: fix set but not used variables
Pulled, thanks.
I was on vacation, but I had a typo in my .procmailrc rule that was
supposed to send the autoreplies... :-/
Michal
prev parent reply other threads:[~2011-08-31 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 0:47 Pending kconfig patches Arnaud Lacombe
2011-08-31 11:50 ` 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=4E5E1FFD.9020105@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).