From: Bart Van Assche <bvanassche@acm.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Genjian Zhang <zhanggenjian@kylinos.cn>,
"Ricardo B. Marliere" <ricardo@marliere.net>,
Sumit Garg <sumit.garg@linaro.org>, Alex Elder <elder@kernel.org>
Subject: Re: [PATCH 2/2] mips: sgi-ip22: Fix the build
Date: Tue, 6 Aug 2024 13:56:51 -0700 [thread overview]
Message-ID: <c41f73c2-be91-450d-ae8c-d0f500d0bbef@acm.org> (raw)
In-Reply-To: <2024080603-buffed-choosy-a04b@gregkh>
On 8/5/24 11:57 PM, Greg Kroah-Hartman wrote:
> On Mon, Aug 05, 2024 at 04:20:21PM -0700, Bart Van Assche wrote:
>> Fix a recently introduced build failure.
>>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Fixes: d69d80484598 ("driver core: have match() callback in struct bus_type take a const *")
>> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
>> ---
>> arch/mips/sgi-ip22/ip22-gio.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>
> Thanks for this, and the other, fix, I'll queue them up to my local
> trees soon. Odd that these two targets do not seem to get any testing
> in that I never was able to see them in the 0-day or other testing bots
> out there. How did you find them?
Some time ago, while making changes in the SCSI core, I noticed that it
is very hard to build all SCSI drivers manually. That is why I wrote a
shell script to cross-compile all SCSI drivers. That script is available
here:
https://github.com/bvanassche/build-scsi-drivers/blob/main/build-scsi-drivers
Thanks,
Bart.
prev parent reply other threads:[~2024-08-06 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 23:20 [PATCH 0/2] Fix recently introduced build failures Bart Van Assche
2024-08-05 23:20 ` [PATCH 1/2] ARM: riscpc: ecard: Fix the build Bart Van Assche
2024-08-05 23:20 ` [PATCH 2/2] mips: sgi-ip22: " Bart Van Assche
2024-08-06 6:57 ` Greg Kroah-Hartman
2024-08-06 20:56 ` Bart Van Assche [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=c41f73c2-be91-450d-ae8c-d0f500d0bbef@acm.org \
--to=bvanassche@acm.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ricardo@marliere.net \
--cc=sumit.garg@linaro.org \
--cc=tsbogend@alpha.franken.de \
--cc=zhanggenjian@kylinos.cn \
/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