All of lore.kernel.org
 help / color / mirror / Atom feed
From: gerlando.falauto@keymile.com (Gerlando Falauto)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] fix MVEBU GPIO driver bug causing kernel hang
Date: Fri, 11 Oct 2013 13:21:19 +0200	[thread overview]
Message-ID: <5257DF2F.5030403@keymile.com> (raw)
In-Reply-To: <CACRpkda39HGthF6n-T8-Rv0nAug9bxi5sqeyTneKoSS9YmRVmw@mail.gmail.com>

Hi LinusW,

what do you mean?
My statement on patch [0/1] contained speculation about a driver which 
is clearly unrelated (the main, generic, orion IRQ controller, which is 
*NOT* what this patch is about). Our discussion with Thomas was about 
this and him explaining how I got the two things confused in my mind.
But the patch, in its real context (the GPIO chip and its interrupt 
handling) should still be sound and needed...
[Patch 0/1] will not be in the commit message anyway...

Thanks,
Gerlando


On 10/11/2013 01:15 PM, Linus Walleij wrote:
> OK I see these comments on patch [0/1] now (how confusing)
> forget what I just said. Patch is dropped.
>
> Yours,
> Linus Walleij
>

  reply	other threads:[~2013-10-11 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 12:31 [PATCH 0/1] fix MVEBU GPIO driver bug causing kernel hang Gerlando Falauto
2013-10-02 12:34 ` [PATCH 1/1] gpio: mvebu: enable and use IRQ_GC_MASK_CACHE_PER_TYPE Gerlando Falauto
2013-10-11 11:13   ` Linus Walleij
2013-10-02 12:45 ` [PATCH 0/1] fix MVEBU GPIO driver bug causing kernel hang Thomas Petazzoni
2013-10-02 13:14   ` Gerlando Falauto
2013-10-02 13:48     ` Thomas Petazzoni
2013-10-11 11:15     ` Linus Walleij
2013-10-11 11:21       ` Gerlando Falauto [this message]
2013-10-11 12:44         ` Linus Walleij

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=5257DF2F.5030403@keymile.com \
    --to=gerlando.falauto@keymile.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.