From: Kalle Valo <kvalo@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: wireless-drivers-next 2015-08-19
Date: Wed, 19 Aug 2015 14:13:46 +0300 [thread overview]
Message-ID: <87bne3a5ud.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87pp2ja6ar.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Wed, 19 Aug 2015 14:03:56 +0300")
Kalle Valo <kvalo@codeaurora.org> writes:
> here's one more pull request for 4.3. More info in the signed tag below.
>
> This time I had to merge mac80211-next.git due to some iwlwifi
> dependencies and apparently that broke git-request-pull's diffstat
> again, it was showing changes which were not really coming from my tree.
> I think that's just a bug in my old git and really should update the
> tool. This time I just fixed the diffstat manually.
>
> But please be extra careful with this pull request and please let me
> know if you have any problems.
Oh, I forgot to mention that I saw this build error when I did a test
merge:
net/ipv4/fib_semantics.c:553:3: error: implicit declaration of function lwtstate_free [-Werror=implicit-function-declaration]
But I see that also with unmodified net-next so I'm assuming I didn't
cause that :)
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull-request: wireless-drivers-next 2015-08-19
Date: Wed, 19 Aug 2015 14:13:46 +0300 [thread overview]
Message-ID: <87bne3a5ud.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87pp2ja6ar.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org> (Kalle Valo's message of "Wed, 19 Aug 2015 14:03:56 +0300")
Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> writes:
> here's one more pull request for 4.3. More info in the signed tag below.
>
> This time I had to merge mac80211-next.git due to some iwlwifi
> dependencies and apparently that broke git-request-pull's diffstat
> again, it was showing changes which were not really coming from my tree.
> I think that's just a bug in my old git and really should update the
> tool. This time I just fixed the diffstat manually.
>
> But please be extra careful with this pull request and please let me
> know if you have any problems.
Oh, I forgot to mention that I saw this build error when I did a test
merge:
net/ipv4/fib_semantics.c:553:3: error: implicit declaration of function lwtstate_free [-Werror=implicit-function-declaration]
But I see that also with unmodified net-next so I'm assuming I didn't
cause that :)
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-08-19 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 11:03 pull-request: wireless-drivers-next 2015-08-19 Kalle Valo
2015-08-19 11:13 ` Kalle Valo [this message]
2015-08-19 11:13 ` Kalle Valo
2015-08-20 21:14 ` David Miller
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=87bne3a5ud.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=davem@davemloft.net \
--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.