From: Kalle Valo <kvalo@codeaurora.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5 wl-drv-next 0/2] register-field manipulation macros
Date: Tue, 26 Jul 2016 16:00:04 +0300 [thread overview]
Message-ID: <87y44od06j.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160725154549.6492cac1@jkicinski-Precision-T1700> (Jakub Kicinski's message of "Mon, 25 Jul 2016 15:45:49 +0100")
Jakub Kicinski <jakub.kicinski@netronome.com> writes:
> On Wed, 6 Jul 2016 17:19:35 +0100, Jakub Kicinski wrote:
>> Hi!
>>
>> I've added few lines about the compilation problems in
>> the commit message of patch 1. I would prefer the mass
>> rename of macros in mt7601u not to be part of this series
>> so patch 2 is left as it was and I'll follow up once this
>> is accepted.
>
> Hi Kalle,
>
> what's the status of this set? It's marked as 'Deferred' in
> linux-wireless patchwork.
Like I said before, I would prefer to see an ack from someone else like
Andrew Morton or Dave Miller. I don't feel comfortable adding new files
to include/ without some sort of support from others. Or maybe Andrew
could even take these directly to his tree?
--
Kalle Valo
next prev parent reply other threads:[~2016-07-26 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 16:19 [PATCHv5 wl-drv-next 0/2] register-field manipulation macros Jakub Kicinski
2016-07-06 16:19 ` [PATCHv5 wl-drv-next 1/2] add basic " Jakub Kicinski
2016-07-06 16:19 ` Jakub Kicinski
2016-07-06 16:19 ` [PATCHv5 wl-drv-next 2/2] mt7601u: use linux/bitfield.h Jakub Kicinski
2016-07-06 16:19 ` Jakub Kicinski
2016-07-25 14:45 ` [PATCHv5 wl-drv-next 0/2] register-field manipulation macros Jakub Kicinski
2016-07-25 14:45 ` Jakub Kicinski
2016-07-26 13:00 ` Kalle Valo [this message]
2016-07-26 13:13 ` Jakub Kicinski
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=87y44od06j.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=jakub.kicinski@netronome.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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.