linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	Peter Huewe <peterhuewe@gmx.de>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Claudiu Beznea <claudiu.beznea@microchip.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] char: tpm: Prepare cleanup of powerpc's asm/prom.h
Date: Fri, 15 Apr 2022 08:44:35 +0000	[thread overview]
Message-ID: <c30543a2-b1dc-4e83-489e-0f8cad34a3ae@csgroup.eu> (raw)
In-Reply-To: <Ykl1ibvVxJUBrhfK@kernel.org>



Le 03/04/2022 à 12:23, Jarkko Sakkinen a écrit :
> On Sat, Apr 02, 2022 at 12:29:19PM +0200, Christophe Leroy wrote:
>> powerpc's asm/prom.h brings some headers that it doesn't
>> need itself.
>>
>> In order to clean it up, first add missing headers in
>> users of asm/prom.h
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> 
> I don't understand this. It changes nothing as far as kernel is concerned.


I sent v2 with a more detailed description.

Thanks
Christophe


> 
>> ---
>>   drivers/char/tpm/tpm_atmel.h   | 2 --
>>   drivers/char/tpm/tpm_ibmvtpm.c | 1 -
>>   2 files changed, 3 deletions(-)
>>
>> diff --git a/drivers/char/tpm/tpm_atmel.h b/drivers/char/tpm/tpm_atmel.h
>> index ba37e77e8af3..959f7cce8301 100644
>> --- a/drivers/char/tpm/tpm_atmel.h
>> +++ b/drivers/char/tpm/tpm_atmel.h
>> @@ -26,8 +26,6 @@ struct tpm_atmel_priv {
>>   
>>   #ifdef CONFIG_PPC64
>>   
>> -#include <asm/prom.h>
>> -
>>   #define atmel_getb(priv, offset) readb(priv->iobase + offset)
>>   #define atmel_putb(val, priv, offset) writeb(val, priv->iobase + offset)
>>   #define atmel_request_region request_mem_region
>> diff --git a/drivers/char/tpm/tpm_ibmvtpm.c b/drivers/char/tpm/tpm_ibmvtpm.c
>> index 3af4c07a9342..1180cce7067a 100644
>> --- a/drivers/char/tpm/tpm_ibmvtpm.c
>> +++ b/drivers/char/tpm/tpm_ibmvtpm.c
>> @@ -20,7 +20,6 @@
>>   #include <linux/spinlock.h>
>>   #include <linux/interrupt.h>
>>   #include <linux/wait.h>
>> -#include <asm/prom.h>
>>   
>>   #include "tpm.h"
>>   #include "tpm_ibmvtpm.h"
>> -- 
>> 2.35.1
>>
> 
> BR, Jarkko

      reply	other threads:[~2022-04-15  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02 10:29 [PATCH] char: agp: Prepare cleanup of powerpc's asm/prom.h Christophe Leroy
2022-04-02 10:29 ` [PATCH] char: tpm: " Christophe Leroy
2022-04-03 10:23   ` Jarkko Sakkinen
2022-04-15  8:44     ` Christophe Leroy [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=c30543a2-b1dc-4e83-489e-0f8cad34a3ae@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=claudiu.beznea@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=peterhuewe@gmx.de \
    /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;
as well as URLs for NNTP newsgroup(s).