From: Hannes Reinecke <hare@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] scsi: clean up generated file scsi_devinfo_tbl.c
Date: Mon, 14 May 2018 07:52:28 +0200 [thread overview]
Message-ID: <20180514075228.784a475f@pentland.suse.de> (raw)
In-Reply-To: <6e64c815-43dd-3945-6c58-66b1e0533403@infradead.org>
On Sun, 13 May 2018 17:10:52 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> "make clean" should remove the generated file "scsi_devinfo_tbl.c",
> so list it in the clean-files variable so that the file gets
> cleaned up.
>
> Fixes: 345e29608b4b ("scsi: scsi: Export blacklist flags to sysfs")
>
> Cc: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/scsi/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-4.17-rc4.orig/drivers/scsi/Makefile
> +++ linux-4.17-rc4/drivers/scsi/Makefile
> @@ -182,7 +182,7 @@ zalon7xx-objs := zalon.o ncr53c8xx.o
> NCR_Q720_mod-objs := NCR_Q720.o ncr53c8xx.o
>
> # Files generated that shall be removed upon make clean
> -clean-files := 53c700_d.h 53c700_u.h
> +clean-files := 53c700_d.h 53c700_u.h scsi_devinfo_tbl.c
>
> $(obj)/53c700.o $(MODVERDIR)/$(obj)/53c700.ver: $(obj)/53c700_d.h
>
>
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
next prev parent reply other threads:[~2018-05-14 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 0:10 [PATCH] scsi: clean up generated file scsi_devinfo_tbl.c Randy Dunlap
2018-05-14 5:52 ` Hannes Reinecke [this message]
2018-05-15 2:48 ` Martin K. Petersen
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=20180514075228.784a475f@pentland.suse.de \
--to=hare@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@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.