From: Michael Ellerman <mpe@ellerman.id.au>
To: mmarek@suse.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] scripts/tags.sh: Teach tags about some powerpc macros
Date: Tue, 13 Oct 2015 16:18:33 +1100 [thread overview]
Message-ID: <1444713513.29347.3.camel@ellerman.id.au> (raw)
In-Reply-To: <1442891295-5222-1-git-send-email-mpe@ellerman.id.au>
On Tue, 2015-09-22 at 13:08 +1000, Michael Ellerman wrote:
> The IO accessors on powerpc are generated using macro fu, ie. out_be32()
> etc. Also there are some debugger related symbols that are macro
> generated. Teach scripts/tags.sh about both.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> scripts/tags.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index 8e5aee6d9da2..262889046703 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -198,6 +198,8 @@ exuberant()
> --regex-c++='/TASK_PFA_TEST\([^,]*,\s*([^)]*)\)/task_\1/' \
> --regex-c++='/TASK_PFA_SET\([^,]*,\s*([^)]*)\)/task_set_\1/' \
> --regex-c++='/TASK_PFA_CLEAR\([^,]*,\s*([^)]*)\)/task_clear_\1/'\
> + --regex-c++='/DEF_MMIO_(IN|OUT)_(X|D)\(([^,]*),\s*[^)]*\)/\3/' \
> + --regex-c++='/DEBUGGER_BOILERPLATE\(([^,]*)\)/\1/' \
> --regex-c='/PCI_OP_READ\((\w*).*[1-4]\)/pci_bus_read_config_\1/' \
> --regex-c='/PCI_OP_WRITE\((\w*).*[1-4]\)/pci_bus_write_config_\1/' \
> --regex-c='/DEFINE_(MUTEX|SEMAPHORE|SPINLOCK)\((\w*)/\2/v/' \
Michal, do you want to take this one or should I ?
cheers
next prev parent reply other threads:[~2015-10-13 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 3:08 [PATCH] scripts/tags.sh: Teach tags about some powerpc macros Michael Ellerman
2015-10-13 5:18 ` Michael Ellerman [this message]
2015-10-13 11:54 ` Michal Marek
2015-10-13 22:56 ` Michael Ellerman
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=1444713513.29347.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mmarek@suse.com \
/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).