linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jaap-Jan Boor <jjboor@aimsys.nl>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Freescale Ethernet combined driver
Date: Thu, 12 May 2005 12:53:03 +0200	[thread overview]
Message-ID: <883b9affce23db0859a4619cff66da4e@aimsys.nl> (raw)
In-Reply-To: <427F4D41.10908@intracom.gr>

Hi,

May be a little late (I'm trying to catch up on all mailing list mail)
but I was wondering if the io port handling functions I see now in 
these patches
should not be 'atomic'. So toggling MII pins does not interfere with 
toggling
e.g. I2C bit-bang interface pins when those pins happen to be on the 
same
port (A/B/C/D/E).

best regards,

Jaap-Jan

  reply	other threads:[~2005-05-12 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 11:45 [PATCH 04/04] Freescale Ethernet combined driver Pantelis Antoniou
2005-05-12 10:53 ` Jaap-Jan Boor [this message]
2005-05-12 10:43   ` [PATCH] " Pantelis Antoniou
2005-05-12 12:50     ` Jaap-Jan Boor

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=883b9affce23db0859a4619cff66da4e@aimsys.nl \
    --to=jjboor@aimsys.nl \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=panto@intracom.gr \
    --cc=trini@kernel.crashing.org \
    /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).