From: Artem Bityutskiy <dedekind1@gmail.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] UBI changes for 2.6.40
Date: Wed, 22 Jun 2011 07:31:10 +0300 [thread overview]
Message-ID: <1308717074.18119.16.camel@sauron> (raw)
In-Reply-To: <20110612064002.GA1712@x4.trippels.de>
Hi Markus,
yes, sorry, this patch was probably a mistake - I just stupidly followed
the new trend.
On Sun, 2011-06-12 at 08:40 +0200, Markus Trippelsdorf wrote:
> Either reverting or using something like this fixes the problem:
However, I am a bit reluctant to revert it now because this would only
hide the issue. And some googling shows that networking people had a
similar error in the past and solved it by reverting before the change
went upstream.
> diff --git a/include/mtd/ubi-user.h b/include/mtd/ubi-user.h
> index 3c41097..47a6c21 100644
> --- a/include/mtd/ubi-user.h
> +++ b/include/mtd/ubi-user.h
> @@ -23,6 +23,10 @@
>
> #include <linux/types.h>
>
> +#ifndef __packed
> +#define __packed __attribute__((packed))
> +#endif
> +
> /*
> * UBI device creation (the same as MTD device attachment)
> * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This would be a dirty hack. I think a better solution is to enhance the
"scripts/headers_install.pl" script and teach it to substitute __packed
with __attribute__((packed)). Then at "make headers_install" time this
issue would be fixed up.
Or may be the definition of __packed has to be somehow included in
ubi-user.h ...
Would you please try to make a patch and send it to lkml to hopefully
generate some discussion and the right way to go would probably be
found?
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2011-06-22 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 6:41 [GIT PULL] UBI changes for 2.6.40 Artem Bityutskiy
2011-06-12 6:40 ` Markus Trippelsdorf
2011-06-22 4:31 ` Artem Bityutskiy [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=1308717074.18119.16.camel@sauron \
--to=dedekind1@gmail.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
/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