All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: tst-atomic
Date: Wed, 4 Apr 2018 15:55:02 +0000	[thread overview]
Message-ID: <1522857302.4851.53.camel@synopsys.com> (raw)
In-Reply-To: <20180313195515.GK2114@waldemar-brodkorb.de>

Hi Waldemar,

On Tue, 2018-03-13@20:55 +0100, Waldemar Brodkorb wrote:
> Hi Alexey,
> Alexey Brodkin wrote,
> 
> > Hi Waldemar,
> > 
> > I see in commit e65912f8b2a6 ("rework most tests to work as standalone package")
> > "tst-atomic" and "tst-atomic-long" were marked as disabled for all architectures
> > as opposed to previously (in times of test-suite being a part of uClibc) disabled
> > only for selected arches (IA64, MIPS and SPARC).
> > 
> > The only guess I have it was done due to inability to refer not-exported "atomic.h".
> > Is that correct? But anyways I'm looking at a possibility to revive those as they
> > might be of use especially in case of emulation of atomics.
> > 
> > Any thoughts on how that could be done?
> 
> Should we export atomic.h again?
> The header is removed since
> 536a0e3a05a0c7d9a4d741d9401c220900cf1e04.

Probably not as this will open again a can with worms.
Fortunately I was able to get my problem understood and almost solved,
I guess you're on Cc list of that discussion here:
http://lists.infradead.org/pipermail/linux-snps-arc/2018-March/003583.html

But then why don't we get rid of ./test/silly/tst-atomic*.c at all?

-Alexey

      reply	other threads:[~2018-04-04 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 14:51 tst-atomic Alexey Brodkin
2018-03-13 19:55 ` tst-atomic Waldemar Brodkorb
2018-04-04 15:55   ` Alexey Brodkin [this message]

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=1522857302.4851.53.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.