[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADZ9YHi34K=MKCKLfjwz07eWK+nDRiggrE4PZE6BPNrHQeABOQ@mail.gmail.com>
Date: Wed, 20 Jul 2011 18:46:07 +0600
From: Rakib Mullick <rakib.mullick@...il.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Jan Beulich <JBeulich@...ell.com>, mingo@...e.hu,
tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: serialize EFI time accesses on rtc_lock
On Tue, Jul 19, 2011 at 11:54 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Tue, Jul 19, 2011 at 11:32:05PM +0600, Rakib Mullick wrote:
> That's just assigning some function pointers, not actually making the
> calls. There's potentially several routes to each of the calls, so it
> makes sense to do the locking there.
>
I got confused by the patch subject. I thought, this serialization is
required at the time of startup.
Thanks,
Rakib
> --
> Matthew Garrett | mjg59@...f.ucam.org
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists