public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Rafael J. Wysocki" <rjw@rjwysocki•net>,
	Huacai Chen <chenhuacai@loongson•cn>
Cc: Bob Moore <robert.moore@intel•com>,
	Huacai Chen <chenhuacai@kernel•org>,
	Jianmin Lv <lvjianmin@loongson•cn>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel•com>
Subject: Re: linux-next: manual merge of the pm tree with the loongarch tree
Date: Thu, 19 May 2022 11:00:08 +1000	[thread overview]
Message-ID: <20220519110008.586bc47f@canb.auug.org.au> (raw)
In-Reply-To: <20220519105448.74a4447e@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

Hi all,

On Thu, 19 May 2022 10:54:48 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>

>  +	u32 count;
>  +};
>  +
>  +/* LPC Interrupt Controller */
>  +
>  +struct acpi_madt_lpc_pic {
>  +	struct acpi_subtable_header header;
>  +	u8 version;
>  +	u64 address;
>  +	u16 size;
>  +	u8 cascade;
> ++
> + /* 17: OEM data */
> + 
> + struct acpi_madt_oem_data {
> + 	u8 oem_data[0];
>   };
>   
>   /*

I missed adding the closing brace after struct acpi_madt_lpc_pic.  I
have added that to my resolution now.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-05-19  1:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  0:54 linux-next: manual merge of the pm tree with the loongarch tree Stephen Rothwell
2022-05-19  1:00 ` Stephen Rothwell [this message]
2022-05-19  1:04   ` Stephen Rothwell
2022-05-19  1:15     ` Huacai Chen

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=20220519110008.586bc47f@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=chenhuacai@kernel$(echo .)org \
    --cc=chenhuacai@loongson$(echo .)cn \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lvjianmin@loongson$(echo .)cn \
    --cc=rafael.j.wysocki@intel$(echo .)com \
    --cc=rjw@rjwysocki$(echo .)net \
    --cc=robert.moore@intel$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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