Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

On Sat, 2016-05-21 at 20:25 -0600, Reinoud Koornstra wrote: > On Fri, May 20, 2016 at 5:41 PM, David Miller > wrote: > > > > From: Kalle Valo > > Date: Thu, 19 May 2016 15:45:08 +0300 > > > > > > > > this the second version of the last pull request

Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

On Fri, May 20, 2016 at 5:41 PM, David Miller wrote: > From: Kalle Valo > Date: Thu, 19 May 2016 15:45:08 +0300 > >> this the second version of the last pull request to net-next for 4.7, >> which got postponed due to the recent iwlwifi merge conflict.

Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

From: Kalle Valo Date: Thu, 19 May 2016 15:45:08 +0300 > this the second version of the last pull request to net-next for 4.7, > which got postponed due to the recent iwlwifi merge conflict. Now that > Linus fixed the merge problem in his tree I actually didn't have to fix

Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

On Thu, May 19, 2016 at 6:45 AM, Kalle Valo wrote: > Hi Dave, > > this the second version of the last pull request to net-next for 4.7, > which got postponed due to the recent iwlwifi merge conflict. Now that > Linus fixed the merge problem in his tree I actually didn't have

pull-request: wireless-drivers-next 2016-05-13 (take two)

Hi Dave, this the second version of the last pull request to net-next for 4.7, which got postponed due to the recent iwlwifi merge conflict. Now that Linus fixed the merge problem in his tree I actually didn't have to fix anything in my tree anymore. So that's why I still use the same tag as in

Re: pull-request: wireless-drivers-next 2016-05-13

David Miller writes: > From: Kalle Valo > Date: Tue, 17 May 2016 09:43:34 +0300 > >> I noticed that you had marked this as Superseded in pathwork[1]. I was >> actually hoping that you would pull this with the instructions how to >> fix the conflict.

Re: pull-request: wireless-drivers-next 2016-05-13

From: Kalle Valo Date: Tue, 17 May 2016 09:43:34 +0300 > I noticed that you had marked this as Superseded in pathwork[1]. I was > actually hoping that you would pull this with the instructions how to > fix the conflict. But do you actually want me to resubmit the pull >

Re: pull-request: wireless-drivers-next 2016-05-13

Hi Dave, Kalle Valo writes: > Kalle Valo writes: > >> Kalle Valo writes: >> >>> >>> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git >>> tags/wireless-drivers-next-for-davem-2016-05-13 >> >>

Re: pull-request: wireless-drivers-next 2016-05-13

On Mon, 2016-05-16 at 17:08 +0300, Kalle Valo wrote: > Kalle Valo writes: > > > > > Kalle Valo writes: > > > > > > > > The following changes since commit > > > ede00a5ceb4d903a8c137a52bb77d574baaef8bd: > > > > > >   Merge tag

Re: pull-request: wireless-drivers-next 2016-05-13

Kalle Valo writes: > Kalle Valo writes: > >> The following changes since commit ede00a5ceb4d903a8c137a52bb77d574baaef8bd: >> >> Merge tag 'wireless-drivers-next-for-davem-2016-05-02' of >>

Re: pull-request: wireless-drivers-next 2016-05-13

Hi Dave, Kalle Valo writes: > this is the last pull request to net-next for 4.7. Nothing really out of > ordinary, the signed tag below contains more info. Please let me know if > there are any issues. > > Kalle > > > The following changes since commit

pull-request: wireless-drivers-next 2016-05-13

Hi Dave, this is the last pull request to net-next for 4.7. Nothing really out of ordinary, the signed tag below contains more info. Please let me know if there are any issues. Kalle The following changes since commit ede00a5ceb4d903a8c137a52bb77d574baaef8bd: Merge tag