All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joel Reardon <joel@clambassador.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: mtdchar kernel oops
Date: Wed, 18 Apr 2012 16:12:04 +0300	[thread overview]
Message-ID: <1334754734.2203.1.camel@koala> (raw)
In-Reply-To: <alpine.DEB.2.00.1204181452410.8114@eristoteles.iwoars.net>

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

On Wed, 2012-04-18 at 14:55 +0200, Joel Reardon wrote:
> Perhaps Artem can shed some light on this, I'm working on a branch he's
> prepared. But if its not happening at your end then perhaps something's up
> on mine; the oops log is rather bizzare. I'll remake it from scratch and
> see what happens.

I am having paternity leave and will not be very responsive for few
weeks from now, sorry. Try to play with rebasing/clean
compilation/changing the compiler etc.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joel Reardon <joel@clambassador.com>
Cc: linux-mtd@lists.infradead.org, Al Viro <viro@ZenIV.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: mtdchar kernel oops
Date: Wed, 18 Apr 2012 16:12:04 +0300	[thread overview]
Message-ID: <1334754734.2203.1.camel@koala> (raw)
In-Reply-To: <alpine.DEB.2.00.1204181452410.8114@eristoteles.iwoars.net>

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

On Wed, 2012-04-18 at 14:55 +0200, Joel Reardon wrote:
> Perhaps Artem can shed some light on this, I'm working on a branch he's
> prepared. But if its not happening at your end then perhaps something's up
> on mine; the oops log is rather bizzare. I'll remake it from scratch and
> see what happens.

I am having paternity leave and will not be very responsive for few
weeks from now, sorry. Try to play with rebasing/clean
compilation/changing the compiler etc.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-04-18 13:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 11:58 mtdchar kernel oops Joel Reardon
2012-04-15 14:19 ` Fabio Estevam
2012-04-15 14:19   ` Fabio Estevam
2012-04-19  0:51   ` Fabio Estevam
2012-04-19  0:51     ` Fabio Estevam
2012-04-15 14:28 ` Richard Weinberger
2012-04-15 14:34   ` Fabio Estevam
2012-04-15 15:32 ` Al Viro
2012-04-15 15:32   ` Al Viro
2012-04-15 17:57   ` Joel Reardon
2012-04-15 17:57     ` Joel Reardon
2012-04-15 21:53     ` Al Viro
2012-04-15 21:53       ` Al Viro
2012-04-16 12:37       ` Joel Reardon
2012-04-16 12:37         ` Joel Reardon
2012-04-16 19:17         ` Al Viro
2012-04-16 19:17           ` Al Viro
2012-04-18 12:55           ` Joel Reardon
2012-04-18 12:55             ` Joel Reardon
2012-04-18 13:12             ` Artem Bityutskiy [this message]
2012-04-18 13:12               ` Artem Bityutskiy

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=1334754734.2203.1.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=joel@clambassador.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.