[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] Should cli() imply a memory barrier?
|
From: |
Jan Waclawek |
|
Subject: |
Re: [avr-libc-dev] Should cli() imply a memory barrier? |
|
Date: |
Tue, 8 Jun 2010 23:49:59 +0200 |
>It's a little unfair that you repost a message to the list which
>you've sent me personally only before, and which I've already replied
>to.
Although I did not mean my post to be private, and reply often as private due
to the nonstandard setting of this forum, you are right.
I apologize.
JW
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Jan Waclawek, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Jan Waclawek, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?,
Jan Waclawek <=
- RE: [avr-libc-dev] Should cli() imply a memory barrier?, Weddington, Eric, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/09