From: Borislav Petkov <bp@alien8.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Johannes Thumshirn <morbidrsa@gmail.com>,
linux-edac@vger.kernel.org, mchehab@kernel.org,
james.morse@arm.com, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] EDAC, mpc85xx: Prevent building as a module
Date: Thu, 9 May 2019 16:55:34 +0200 [thread overview]
Message-ID: <20190509145534.GD17053@zn.tnic> (raw)
In-Reply-To: <87o94bvfxm.fsf@concordia.ellerman.id.au>
On Fri, May 10, 2019 at 12:52:05AM +1000, Michael Ellerman wrote:
> Thanks. It would be nice if you could send it as a fix for 5.2, it's the
> last thing blocking one of my allmodconfig builds. But if you don't
> think it qualifies as a fix that's fine too, it can wait.
Sure, no problem. Will do a pull request later.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Johannes Thumshirn <morbidrsa@gmail.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
james.morse@arm.com, mchehab@kernel.org,
linux-edac@vger.kernel.org
Subject: Re: [PATCH] EDAC, mpc85xx: Prevent building as a module
Date: Thu, 9 May 2019 16:55:34 +0200 [thread overview]
Message-ID: <20190509145534.GD17053@zn.tnic> (raw)
In-Reply-To: <87o94bvfxm.fsf@concordia.ellerman.id.au>
On Fri, May 10, 2019 at 12:52:05AM +1000, Michael Ellerman wrote:
> Thanks. It would be nice if you could send it as a fix for 5.2, it's the
> last thing blocking one of my allmodconfig builds. But if you don't
> think it qualifies as a fix that's fine too, it can wait.
Sure, no problem. Will do a pull request later.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-05-09 14:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 14:19 [PATCH] EDAC, mpc85xx: Prevent building as a module Michael Ellerman
2019-05-02 14:19 ` Michael Ellerman
2019-05-06 6:50 ` Johannes Thumshirn
2019-05-06 6:50 ` Johannes Thumshirn
2019-05-08 10:12 ` Borislav Petkov
2019-05-08 10:12 ` Borislav Petkov
2019-05-09 14:52 ` Michael Ellerman
2019-05-09 14:52 ` Michael Ellerman
2019-05-09 14:55 ` Borislav Petkov [this message]
2019-05-09 14:55 ` Borislav Petkov
2019-05-09 18:02 ` Borislav Petkov
2019-05-09 18:02 ` Borislav Petkov
2019-05-10 10:50 ` Michael Ellerman
2019-05-10 10:50 ` Michael Ellerman
2019-05-10 14:13 ` Borislav Petkov
2019-05-10 14:13 ` Borislav Petkov
2019-05-10 18:25 ` Borislav Petkov
2019-05-10 18:25 ` Borislav Petkov
2019-05-14 6:50 ` Michael Ellerman
2019-05-14 6:50 ` Michael Ellerman
2019-05-14 8:31 ` Borislav Petkov
2019-05-14 8:31 ` Borislav Petkov
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=20190509145534.GD17053@zn.tnic \
--to=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mchehab@kernel.org \
--cc=morbidrsa@gmail.com \
--cc=mpe@ellerman.id.au \
/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.