From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Yiyyh-0001A4-S1 for kexec@lists.infradead.org; Fri, 17 Apr 2015 05:38:12 +0000 Message-ID: <55309C29.5050702@redhat.com> Date: Fri, 17 Apr 2015 11:07:45 +0530 From: Pratyush Anand MIME-Version: 1.0 Subject: Re: [PATCH RFC 6/6] arm64: wait for transmit completion before next character transmission References: <6c8a63f701e98cb7cf4ddd96ab5b509115ebdc41.1429201849.git.panand@redhat.com> <20150417053621.GA8658@dhcp-128-1.nay.redhat.com> In-Reply-To: <20150417053621.GA8658@dhcp-128-1.nay.redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: Minfei Huang Cc: kexec@lists.infradead.org, kexec@lists.fedoraproject.org On Friday 17 April 2015 11:06 AM, Minfei Huang wrote: >> .quad 0 >> > size arm64_dtb_addr >> >+ >> >+.globl arm64_sink_lsr_val >> >+arm64_sink_lsr_val: >> >+ .word 0 > Since arm64_sink_lsr_val is declared as uint32_t, it is better to keep > the same format here. > I thought .word will do the same. But may be I am wrong. What is the good syntax for uint32_t. ~Pratyush _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec