[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-libc-dev] Should cli() imply a memory barrier?
From: |
Weddington, Eric |
Subject: |
RE: [avr-libc-dev] Should cli() imply a memory barrier? |
Date: |
Tue, 8 Jun 2010 15:59:32 -0600 |
> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Jan Waclawek
> Sent: Tuesday, June 08, 2010 3:50 PM
> To: Joerg Wunsch; address@hidden
> Subject: Re: [avr-libc-dev] Should cli() imply a memory barrier?
>
> >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.
It's pretty easy to click on "Reply All". It becomes a force of habit after
posting on multiple mailing lists over several projects.
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, (continued)
- 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, 2010/06/08
- RE: [avr-libc-dev] Should cli() imply a memory barrier?,
Weddington, Eric <=
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/09