public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Siegmund, Thomas" <thomas.siegmund@hach-lange.de>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: AW: [ECOS] __attribute__ ((packed)) doesn't work
Date: Wed, 22 Feb 2006 15:05:00 -0000	[thread overview]
Message-ID: <211AD5A0EF29B84B9B2736BAF71657B775A03D@dhreinsvxb02.messaging.danaherad.com> (raw)

Thanks for your answer about the court ;-))...
Hopefully this attachment won't appear now.

Well, and what about the "usb_endpoint_descriptor" which doesn't own this attribute? 
My assumption is it is missing, isn't it? 
Concerning a patch I'm not familiar to create this one because I'm a newbie. Can
you tell me where some documentation about it are placed?

Thomas

 

-----Ursprüngliche Nachricht-----
Von: Andrew Lunn [mailto:andrew@lunn.ch] 
Gesendet: Mittwoch, 22. Februar 2006 15:49
An: Siegmund, Thomas
Cc: ecos-discuss@ecos.sourceware.org
Betreff: Re: [ECOS] __attribute__ ((packed)) doesn't work

On Wed, Feb 22, 2006 at 01:42:26PM +0100, Siegmund, Thomas wrote:
> Sorry for that but I don't have an influence to discard this attachment. 
> I only can apologize myself but I really would appreciate to get a 
> technical hint.

OK, so long as you agree not to take me to court!

The USB stack was tested on ARM with gcc 3.2.1. GCC is getting more picky about where the attributes are placed. I think that the version you are using is simply ignoring them. You change is correct. If you submit a proper patch i will see about comitting it.

        Andrew

This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law.  If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system.  If you
have any questions about this e-mail please notify the sender
immediately.

Ce message (ainsi que les eventuelles pieces jointes) est
exclusivement adresse au destinataire et contient des
informations confidentielles. La copie, la communication ou la
distribution du contenu de ce message sans l'accord prealable de
l'expediteur sont strictement interdits et peuvent constituer un
delit. Si vous n'etes pas destinataire de ce message, merci de le
detruire et d'avertir l'expediteur. Si vous avez des questions se
rapportant a ce courrier electronique, merci de bien vouloir
notifier
l'expediteur immediatement.

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-02-22 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 15:05 Siegmund, Thomas [this message]
2006-02-22 15:37 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2006-02-23 15:27 AW: " Siegmund, Thomas
2006-02-22 12:42 Siegmund, Thomas

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=211AD5A0EF29B84B9B2736BAF71657B775A03D@dhreinsvxb02.messaging.danaherad.com \
    --to=thomas.siegmund@hach-lange.de \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).