From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Baoquan He <bhe@redhat.com>, rjw@rjwysocki.net, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / tables: Cleanup the obsolete acpi_parse_entries
Date: Tue, 11 Apr 2017 14:31:32 +0800 [thread overview]
Message-ID: <58EC7844.9020401@cn.fujitsu.com> (raw)
In-Reply-To: <1491553367-17847-1-git-send-email-bhe@redhat.com>
On 04/07/2017 04:22 PM, Baoquan He wrote:
> Function acpi_parse_entries is not used any more. And the being used
> function, acpi_table_parse_entries can substitute it if really needed.
>
> So clean it up in this patch.
>
It maybe also useful to mention the commit id f26527b142 & 9b3fedde27
who disuse the function.
--
Sincerely,
Cao jin
WARNING: multiple messages have this Message-ID (diff)
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Baoquan He <bhe@redhat.com>, <rjw@rjwysocki.net>, <lenb@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / tables: Cleanup the obsolete acpi_parse_entries
Date: Tue, 11 Apr 2017 14:31:32 +0800 [thread overview]
Message-ID: <58EC7844.9020401@cn.fujitsu.com> (raw)
In-Reply-To: <1491553367-17847-1-git-send-email-bhe@redhat.com>
On 04/07/2017 04:22 PM, Baoquan He wrote:
> Function acpi_parse_entries is not used any more. And the being used
> function, acpi_table_parse_entries can substitute it if really needed.
>
> So clean it up in this patch.
>
It maybe also useful to mention the commit id f26527b142 & 9b3fedde27
who disuse the function.
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2017-04-11 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 8:22 [PATCH] ACPI / tables: Cleanup the obsolete acpi_parse_entries Baoquan He
2017-04-11 6:31 ` Cao jin [this message]
2017-04-11 6:31 ` Cao jin
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=58EC7844.9020401@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=bhe@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.