From: Kalle Valo <kvalo@codeaurora.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 1/2] mt76x0: raname mt76_* functions
Date: Fri, 03 Aug 2018 19:24:19 +0300 [thread overview]
Message-ID: <87muu35sgc.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180803161828.GA2389@redhat.com> (Stanislaw Gruszka's message of "Fri, 3 Aug 2018 18:18:29 +0200")
Stanislaw Gruszka <sgruszka@redhat.com> writes:
> On Fri, Aug 03, 2018 at 07:08:23PM +0300, Kalle Valo wrote:
>> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>>
>> > mt76_* functions conflicts with mt7601u driver what prevents to build
>> > those drivers in the kernel or use both drivers modules at once.
>> >
>> > Patch fixes build errors like this:
>> > ld: drivers/net/wireless/mediatek/mt76/mt76x0/mac.o:(.opd+0x30):
>> > multiple definition of `mt76_mac_tx_rate_val';
>> > drivers/net/wireless/mediatek/mt7601u/mac.o:(.opd+0x30): first
>> > defined here
>> >
>> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
>>
>> Thanks. I'll add this to both patches:
>>
>> Fixes: 7b4859026ccd ("mt76x0: core files")
>
> Please also fix typo in the topic raname -> rename
Oh, I didn't even notice that. Will fix.
The patches are now in w-d-next pending branch and I'll also run some
build tests myself. If everything goes ok I'll apply these.
--
Kalle Valo
next prev parent reply other threads:[~2018-08-03 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 11:44 [PATCH 1/2] mt76x0: raname mt76_* functions Stanislaw Gruszka
2018-08-03 11:44 ` [PATCH 2/2] mt76x0: rename trace symbols Stanislaw Gruszka
2018-08-03 16:08 ` [PATCH 1/2] mt76x0: raname mt76_* functions Kalle Valo
2018-08-03 16:18 ` Stanislaw Gruszka
2018-08-03 16:24 ` Kalle Valo [this message]
2018-08-04 6:07 ` [PATCH 1/2] mt76x0: rename " Kalle Valo
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=87muu35sgc.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sgruszka@redhat.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 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.