From: Jes Sorensen <jes@sgi.com>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-scsi@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH] qla1280: use request_firmware
Date: Mon, 14 Jul 2008 16:03:31 +0200 [thread overview]
Message-ID: <487B5CB3.60207@sgi.com> (raw)
In-Reply-To: <1216039088.10198.8.camel@jaswinder.satnam>
Jaswinder Singh wrote:
> We have not changed the data.
> We are passing risc_code01 data by using request_firmware when required.
>
> If you found some problem in the code, Please let me know.
My issue was not about changing the format of the data, but about it
being forced into userland, ie. requiring an initrd. After speaking to
Woodhouse over irc, I have learned that with the new firmware
infrastructure this is optional and one can still link the firmware into
the kernel.
Given that the previous firmware moving patches have always been about
getting firmware out of the kernel due to certain distro's being silly
about it, this wasn't actually obvious. If your patch description had
been a little more detailed and explained that it didn't require
firmware to go into userland it would have been easier for someone who
hasn't been following the previous thread on the subject.
So, I don't have any objections to this patch as long as the new
firmware interface continues to allow me to link this into the kernel.
Regards,
Jes
next prev parent reply other threads:[~2008-07-14 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1215770284.2733.10.camel@jaswinder.satnam>
2008-07-14 9:29 ` [PATCH] qla1280: use request_firmware Jes Sorensen
2008-07-14 12:38 ` Jaswinder Singh
2008-07-14 14:03 ` Jes Sorensen [this message]
2008-07-14 13:59 ` David Woodhouse
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=487B5CB3.60207@sgi.com \
--to=jes@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=jaswinder@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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