From: Michal Marek <mmarek@suse.cz>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] genksyms: Ignore changes to internal files
Date: Wed, 02 Nov 2011 00:26:12 +0100 [thread overview]
Message-ID: <4EB08014.8010004@suse.cz> (raw)
In-Reply-To: <1318327969-24807-1-git-send-email-mmarek@suse.cz>
On 11.10.2011 12:12, Michal Marek wrote:
> Hi,
>
> this series teaches genksyms to ignore changes to internal files (those
> defined in the source file itself). See patch 2/3 for the main part.
>
> Michal
>
>
> Michal Marek (3):
> genksyms: Minor parser cleanup
> genksyms: Do not expand internal types
> genksyms: Regenerate lexer and parser
Looks like nobody besides me cares about genksyms :). I applied this to
my kbuild branch now.
Michal
prev parent reply other threads:[~2011-11-01 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 10:12 [PATCH 0/3] genksyms: Ignore changes to internal files Michal Marek
2011-10-11 10:12 ` [PATCH 1/3] genksyms: Minor parser cleanup Michal Marek
2011-10-11 10:12 ` [PATCH 2/3] genksyms: Do not expand internal types Michal Marek
2011-10-11 10:12 ` [PATCH 3/3] genksyms: Regenerate lexer and parser Michal Marek
2011-10-11 10:13 ` [PATCH 0/3] genksyms: Ignore changes to internal files Michal Marek
2011-11-01 23:26 ` 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=4EB08014.8010004@suse.cz \
--to=mmarek@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox