All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <julien.thierry@arm.com>, <marc.zyngier@arm.com>
Cc: peterz@infradead.org, tglx@linutronix.de, yj.chiang@mediatek.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: Remove warning on preemptible in prepare_percpu_nmi()
Date: Thu, 20 Jun 2019 18:50:24 +0800	[thread overview]
Message-ID: <20190620105024.24935-1-lecopzer.chen@mediatek.com> (raw)
In-Reply-To: <20190620091233.22731-1-lecopzer.chen@mediatek.com>

Thanks a lot for reply!!

I just misunderstood how a PPI is registered and thought
I have a chance to eliminate the code.
This patch seems nonsense now, please ignore it.

Sorry to disturb you guys.


Thanks,
	Lecopzer

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <julien.thierry@arm.com>, <marc.zyngier@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <tglx@linutronix.de>,
	<peterz@infradead.org>, <yj.chiang@mediatek.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] genirq: Remove warning on preemptible in prepare_percpu_nmi()
Date: Thu, 20 Jun 2019 18:50:24 +0800	[thread overview]
Message-ID: <20190620105024.24935-1-lecopzer.chen@mediatek.com> (raw)
In-Reply-To: <20190620091233.22731-1-lecopzer.chen@mediatek.com>

Thanks a lot for reply!!

I just misunderstood how a PPI is registered and thought
I have a chance to eliminate the code.
This patch seems nonsense now, please ignore it.

Sorry to disturb you guys.


Thanks,
	Lecopzer

  parent reply	other threads:[~2019-06-20 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  9:12 [PATCH] genirq: Remove warning on preemptible in prepare_percpu_nmi() Lecopzer Chen
2019-06-20  9:12 ` Lecopzer Chen
2019-06-20  9:40 ` Marc Zyngier
2019-06-20  9:40   ` Marc Zyngier
2019-06-20  9:44 ` Julien Thierry
2019-06-20  9:44   ` Julien Thierry
2019-06-20 10:50 ` Lecopzer Chen [this message]
2019-06-20 10:50   ` Lecopzer Chen

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=20190620105024.24935-1-lecopzer.chen@mediatek.com \
    --to=lecopzer.chen@mediatek.com \
    --cc=julien.thierry@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=yj.chiang@mediatek.com \
    /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.