From: Borislav Petkov <bp@alien8.de>
To: "Chen, Gong" <gong.chen@linux.intel.com>
Cc: tony.luck@intel.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH V2] ACPI, APEI: Cleanup alignment related codes for APEI
Date: Thu, 14 Nov 2013 13:29:56 +0100 [thread overview]
Message-ID: <20131114122956.GE13376@pd.tnic> (raw)
In-Reply-To: <20131114014924.GA17790@gchen.bj.intel.com>
On Wed, Nov 13, 2013 at 08:49:24PM -0500, Chen, Gong wrote:
> On Sun, Nov 10, 2013 at 09:07:46PM -0500, Chen, Gong wrote:
> > Date: Sun, 10 Nov 2013 21:07:46 -0500
> > From: "Chen, Gong" <gong.chen@linux.intel.com>
> > To: tony.luck@intel.com, bp@alien8.de
> > Cc: linux-acpi@vger.kernel.org, "Chen, Gong" <gong.chen@linux.intel.com>
> > Subject: [PATCH V2] ACPI, APEI: Cleanup alignment related codes for APEI
> > X-Mailer: git-send-email 1.8.4.rc3
> >
> > We ever used *memcpy* to avoid access alignment issue between
> > firmware and OS. Now we can use a better and standard way
> > to avoid this issue. In the meanwhile, simplify some variable names
> > to avoid the limit of 80 characters per line and use structure
> > assignment instead of unnecessary memcpy. No functional changes.
> >
> > v2->v1: Make description information clearer.
> >
> Any comments? Boris/Tony?
I get this when building here:
drivers/acpi/apei/apei-base.c: In function ‘apei_check_gar’:
drivers/acpi/apei/apei-base.c:571:8: warning: assignment makes pointer from integer without a cast [enabled by default]
paddr = get_unaligned(®->address);
^
drivers/acpi/apei/apei-base.c: In function ‘collect_res_callback’:
drivers/acpi/apei/apei-base.c:716:3: warning: ‘paddr’ may be used uninitialized in this function [-Wmaybe-uninitialized]
return apei_res_add(&resources->iomem, paddr,
^
drivers/acpi/apei/apei-base.c: In function ‘apei_read’:
drivers/acpi/apei/apei-base.c:645:10: warning: ‘address’ may be used uninitialized in this function [-Wmaybe-uninitialized]
status = acpi_os_read_memory((acpi_physical_address) address,
^
drivers/acpi/apei/apei-base.c: In function ‘apei_write’:
drivers/acpi/apei/apei-base.c:678:10: warning: ‘address’ may be used uninitialized in this function [-Wmaybe-uninitialized]
status = acpi_os_write_memory((acpi_physical_address) address,
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-14 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 2:07 [PATCH V2] ACPI, APEI: Cleanup alignment related codes for APEI Chen, Gong
2013-11-14 1:49 ` Chen, Gong
2013-11-14 12:29 ` Borislav Petkov [this message]
2013-11-15 5:38 ` Chen, Gong
2013-11-15 5:45 ` [PATCH v3] " Chen, Gong
2013-11-16 11:48 ` Borislav Petkov
2013-12-14 13:41 ` Chen, Gong
2013-12-14 16:45 ` Borislav Petkov
2013-12-16 14:19 ` Borislav Petkov
2013-12-16 14:39 ` Chen, Gong
2013-12-16 17:55 ` Borislav Petkov
2013-12-17 5:34 ` Chen, Gong
2013-12-17 15:17 ` Borislav Petkov
2013-12-18 6:30 ` [PATCH v4] " Chen, Gong
2013-12-18 21:13 ` Borislav Petkov
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=20131114122956.GE13376@pd.tnic \
--to=bp@alien8.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).