All of lore.kernel.org
 help / color / mirror / Atom feed
From: gmbnomis@gmail.com (Simon Baatz)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.5-rc1 ARM PXA possible regression
Date: Mon, 04 Jun 2012 21:32:34 +0200	[thread overview]
Message-ID: <4FCD0D52.7020602@gmail.com> (raw)
In-Reply-To: <87fwab88o5.fsf@lebrac.rtp-net.org>

Hi Arnaud,

Am 04.06.2012 16:15, schrieb Arnaud Patard (Rtp):
> There has been discussions here about that iirc. I don't know when a
> proper fix will be merged but one *very* *ugly* workaround is:
>
> --- linux.orig/kernel/printk.c  2012-06-03 15:26:20.000000000 +0200
> +++ linux/kernel/printk.c       2012-06-03 16:41:24.000000000 +0200
> @@ -228,7 +228,7 @@ static u32 clear_idx;
>  
>  /* record buffer */
>  #if !defined(CONFIG_64BIT) || defined(CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS)
> -#define LOG_ALIGN 4
> +#define LOG_ALIGN 8
>  #else
>  #define LOG_ALIGN 8
>  #endif
>
>
> At least it seems to work here.

Yes, a thread discussing this is at
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-May/101783.html
, which did not really come to a conclusion, but proposed the following
fix (the original proposal used "struct log_buf", but it should be
"struct log" I suppose):

/#define LOG_ALIGN (__alignof__(struct log))

/which works for me on kirkwood (but apparently may waste a couple of bytes on other architectures)


- Simon

  parent reply	other threads:[~2012-06-04 19:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 14:05 v3.5-rc1 ARM PXA possible regression Andrew Lunn
2012-06-04 14:15 ` Arnaud Patard (Rtp)
2012-06-04 15:23   ` Paul Parsons
2012-06-04 19:32   ` Simon Baatz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-04 12:35 Paul Parsons
2012-06-05  2:44 ` Eric Miao

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=4FCD0D52.7020602@gmail.com \
    --to=gmbnomis@gmail.com \
    --cc=linux-arm-kernel@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.