From: Baoquan He <bhe@redhat.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"lenb@kernel.org" <lenb@kernel.org>,
"Schmauss, Erik" <erik.schmauss@intel.com>
Subject: Re: [PATCH] ACPICA: Clean up whitespace of indentation
Date: Wed, 8 Nov 2017 10:10:02 +0800 [thread overview]
Message-ID: <20171108021002.GH22644@x1> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37E6183BD@ORSMSX110.amr.corp.intel.com>
On 11/07/17 at 03:09pm, Moore, Robert wrote:
> Anything like this probably happens during the conversion of ACPICA code to Linux-style code. This conversion happens after every release (monthly) of ACPICA.
>
> Specifically indent/lindent seems to do things like this, if I remember correctly.
I found it when went through system init code, it was introduced in this
commit and looks very obvious:
commit 19d0cfe9ddfdf7afa8d1765ab0bd2a7dd30e47c9
Author: Bob Moore <robert.moore@intel.com>
Date: Tue Jun 10 15:54:40 2008 +0800
ACPICA: Update DMAR and SRAT table definitions
If there has been a mechanism to check them, I am fine to leave it as is
or the tools like lindent to deal with it.
Thanks
Baoquan
>
> > -----Original Message-----
> > From: Baoquan He [mailto:bhe@redhat.com]
> > Sent: Tuesday, November 7, 2017 2:43 AM
> > To: linux-kernel@vger.kernel.org; linux-acpi@vger.kernel.org
> > Cc: rjw@rjwysocki.net; lenb@kernel.org; Moore, Robert
> > <robert.moore@intel.com>; Zheng, Lv <lv.zheng@intel.com>
> > Subject: Re: [PATCH] ACPICA: Clean up whitespace of indentation
> >
> > PING!
> >
> > On 10/28/17 at 09:34am, Baoquan He wrote:
> > > Use tabs (not spaces) for indentation.
> > >
> > > Signed-off-by: Baoquan He <bhe@redhat.com>
> > > ---
> > > include/acpi/actbl1.h | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/include/acpi/actbl1.h b/include/acpi/actbl1.h index
> > > 6b8714a428b6..d8a4fc066abe 100644
> > > --- a/include/acpi/actbl1.h
> > > +++ b/include/acpi/actbl1.h
> > > @@ -1438,9 +1438,9 @@ struct acpi_srat_mem_affinity {
> > > u16 reserved; /* Reserved, must be zero */
> > > u64 base_address;
> > > u64 length;
> > > - u32 reserved1;
> > > + u32 reserved1;
> > > u32 flags;
> > > - u64 reserved2; /* Reserved, must be zero */
> > > + u64 reserved2; /* Reserved, must be zero */
> > > };
> > >
> > > /* Flags */
> > > --
> > > 2.5.5
> > >
prev parent reply other threads:[~2017-11-08 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 1:34 [PATCH] ACPICA: Clean up whitespace of indentation Baoquan He
2017-11-07 10:43 ` Baoquan He
2017-11-07 15:09 ` Moore, Robert
2017-11-08 2:10 ` Baoquan He [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=20171108021002.GH22644@x1 \
--to=bhe@redhat.com \
--cc=erik.schmauss@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.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