From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] Irq/mbigen:Change the mbigen driver based on the new mbigen node definition.
Date: Mon, 14 Mar 2016 08:44:08 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1603140841560.3657@nanos> (raw)
In-Reply-To: <1457937907-14008-3-git-send-email-majun258@huawei.com>
On Mon, 14 Mar 2016, MaJun wrote:
> From: Ma Jun <majun258@huawei.com>
>
> To fix the IO remap problem, change the mbigen driver based on the
> new mbigen node definition.
Please describe what the problem is. There is no way that anyone can figure
out why that patch is required, what it fixes and how the fix is done. The
'how' should be a high level description as we can see the actual changes in
the diff.
Thanks,
tglx
prev parent reply other threads:[~2016-03-14 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 6:45 [PATCH v2 0/2] Irq/Mbigen: fix the IO remap problem in mbigen driver MaJun
2016-03-14 6:45 ` [PATCH v2 1/2] Irq/mbigen:Change the mbigen node definition in dt binding file MaJun
2016-03-14 7:49 ` Thomas Gleixner
2016-03-15 7:35 ` majun (F)
2016-03-14 6:45 ` [PATCH v2 2/2] Irq/mbigen:Change the mbigen driver based on the new mbigen node definition MaJun
2016-03-14 7:44 ` Thomas Gleixner [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=alpine.DEB.2.11.1603140841560.3657@nanos \
--to=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox