From: Arend van Spriel <arend@broadcom.com>
To: Fariya <fariyaf@gmail.com>
Cc: <backports@vger.kernel.org>
Subject: Re: Procedure to make the driver into the backports project
Date: Mon, 26 May 2014 16:15:42 +0200 [thread overview]
Message-ID: <53834C8E.5020903@broadcom.com> (raw)
In-Reply-To: <53834533.8030800@broadcom.com>
On 05/26/14 15:44, Arend van Spriel wrote:
> On 05/26/14 11:47, Fariya wrote:
>> Hi,
>>
>> My company's wireless driver is a part of the latest 3.15-rc kernel.
>> My question is pertaining to the backports project. How does the
>> procedure at backports work? Will my driver be picked up and
>> backported by the backports group now that it is part of the kernel or
>> the owner of the driver needs to backport the driver [for various
>> kernels] and provide it on to this mailing list initially?
>
> The backport repo does not hold a backported driver, but a framework to
> create a package of the latest drivers which can be automatically
> backported to various kernels.
>
> When you check out the backports repository on kernel.org there is a
> copy-list file which lists everything that is copied from the kernel
> tree to be included in the backport package. First step would be to add
> you driver to that list. If you are lucky that might be sufficient.
However, a quick try over here shows not :-p
/tmp/backporst-rsi/drivers/net/wireless/rsi/rsi_91x_mac80211.c: In
function rsi_mac80211_attach:
/tmp/backporst-rsi/drivers/net/wireless/rsi/rsi_91x_mac80211.c:988:2:
error: implicit declaration of function ether_addr_copy
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[7]: ***
[/tmp/backporst-rsi/drivers/net/wireless/rsi/rsi_91x_mac80211.o] Error 1
Regards,
Arend
> Regards,
> Arend
>
>> Regards,
>> Fariya
>> --
>> To unsubscribe from this list: send the line "unsubscribe backports" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-26 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 9:47 Procedure to make the driver into the backports project Fariya
2014-05-26 13:44 ` Arend van Spriel
2014-05-26 14:15 ` Arend van Spriel [this message]
2014-05-29 10:03 ` Fariya
2014-05-29 14:39 ` Arend van Spriel
[not found] ` <CAG+h2qjirPQYDnajR-3VBvZgr+TxBkMwS3q5xXUrNC+YQmfuog@mail.gmail.com>
2014-06-05 21:30 ` Fariya
2014-06-05 21:55 ` Arend van Spriel
2014-06-05 23:59 ` Fariya
2014-06-06 6:09 ` Johannes Berg
2014-06-06 8:09 ` Arend van Spriel
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=53834C8E.5020903@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=fariyaf@gmail.com \
/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