Alexander Gordeev writes:
> Signed-off-by: Alexander Gordeev
Thanks, all three patches applied to my ath.git tree.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Wed, Feb 12, 2014 at 11:30:44PM +0200, Kalle Valo wrote:
> Bjorn Helgaas writes:
>
> >> Well, as this series is small I thought it could quickly go thru your
> >> tree. But since ipr had conflicts, there is no point routing all patches
> >> altogether, so up to you guys. The wil6210 patch is
Bjorn Helgaas writes:
> On Wed, Feb 12, 2014 at 2:30 PM, Kalle Valo wrote:
>> Bjorn Helgaas writes:
>>
Well, as this series is small I thought it could quickly go thru your
tree. But since ipr had conflicts, there is no point routing all patches
altogether, so up to you guys.
Bjorn Helgaas bhelg...@google.com writes:
On Wed, Feb 12, 2014 at 2:30 PM, Kalle Valo kv...@qca.qualcomm.com wrote:
Bjorn Helgaas bhelg...@google.com writes:
Well, as this series is small I thought it could quickly go thru your
tree. But since ipr had conflicts, there is no point routing all
On Wed, Feb 12, 2014 at 11:30:44PM +0200, Kalle Valo wrote:
Bjorn Helgaas bhelg...@google.com writes:
Well, as this series is small I thought it could quickly go thru your
tree. But since ipr had conflicts, there is no point routing all patches
altogether, so up to you guys. The wil6210
Alexander Gordeev agord...@redhat.com writes:
Signed-off-by: Alexander Gordeev agord...@redhat.com
Thanks, all three patches applied to my ath.git tree.
--
Kalle Valo
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
On Wed, Feb 12, 2014 at 2:30 PM, Kalle Valo wrote:
> Bjorn Helgaas writes:
>
>>> Well, as this series is small I thought it could quickly go thru your
>>> tree. But since ipr had conflicts, there is no point routing all patches
>>> altogether, so up to you guys. The wil6210 patch is already in
Bjorn Helgaas writes:
>> Well, as this series is small I thought it could quickly go thru your
>> tree. But since ipr had conflicts, there is no point routing all patches
>> altogether, so up to you guys. The wil6210 patch is already in your pci/msi
>> branch though.
>
> It's in pci/msi, but
On Wed, Feb 12, 2014 at 6:38 AM, Alexander Gordeev wrote:
> On Tue, Feb 11, 2014 at 05:31:43PM -0700, Bjorn Helgaas wrote:
>> I haven't put these in my branch, so you can take them.
>>
>> Alexander has a whole batch of network driver updates that I think David
>> Miller is going to apply; would
On Tue, Feb 11, 2014 at 05:31:43PM -0700, Bjorn Helgaas wrote:
> I haven't put these in my branch, so you can take them.
>
> Alexander has a whole batch of network driver updates that I think David
> Miller is going to apply; would it make sense to include these in that
> batch?
>
> There's also
On Tue, Feb 11, 2014 at 05:31:43PM -0700, Bjorn Helgaas wrote:
I haven't put these in my branch, so you can take them.
Alexander has a whole batch of network driver updates that I think David
Miller is going to apply; would it make sense to include these in that
batch?
There's also the
On Wed, Feb 12, 2014 at 6:38 AM, Alexander Gordeev agord...@redhat.com wrote:
On Tue, Feb 11, 2014 at 05:31:43PM -0700, Bjorn Helgaas wrote:
I haven't put these in my branch, so you can take them.
Alexander has a whole batch of network driver updates that I think David
Miller is going to
Bjorn Helgaas bhelg...@google.com writes:
Well, as this series is small I thought it could quickly go thru your
tree. But since ipr had conflicts, there is no point routing all patches
altogether, so up to you guys. The wil6210 patch is already in your pci/msi
branch though.
It's in
On Wed, Feb 12, 2014 at 2:30 PM, Kalle Valo kv...@qca.qualcomm.com wrote:
Bjorn Helgaas bhelg...@google.com writes:
Well, as this series is small I thought it could quickly go thru your
tree. But since ipr had conflicts, there is no point routing all patches
altogether, so up to you guys. The
On Wed, Feb 05, 2014 at 10:54:37AM +0200, Kalle Valo wrote:
> Alexander Gordeev writes:
>
> > On Wed, Feb 05, 2014 at 10:21:28AM +0200, Kalle Valo wrote:
> >> Is it ok for me to take these patches to my ath.git tree or would you
> >> prefer to route them some other way?
> >
> > Yeah, Bjorn has
On Wed, Feb 05, 2014 at 10:54:37AM +0200, Kalle Valo wrote:
Alexander Gordeev agord...@redhat.com writes:
On Wed, Feb 05, 2014 at 10:21:28AM +0200, Kalle Valo wrote:
Is it ok for me to take these patches to my ath.git tree or would you
prefer to route them some other way?
Yeah, Bjorn
Alexander Gordeev writes:
> On Wed, Feb 05, 2014 at 10:21:28AM +0200, Kalle Valo wrote:
>> Is it ok for me to take these patches to my ath.git tree or would you
>> prefer to route them some other way?
>
> Yeah, Bjorn has indicated he would pull it to his tree.
Ok, I'll drop these from my
On Wed, Feb 05, 2014 at 10:21:28AM +0200, Kalle Valo wrote:
> Is it ok for me to take these patches to my ath.git tree or would you
> prefer to route them some other way?
Yeah, Bjorn has indicated he would pull it to his tree.
I get it you are fine with 2/3 and 3/3?
--
Regards,
Alexander
Alexander Gordeev writes:
> On Tue, Feb 04, 2014 at 08:32:12PM +0200, Kalle Valo wrote:
>> Alexander Gordeev writes:
>>
>> I don't understand how this is superfluous. When I read the
>> documentation for pci_enable_msi_block() it states that if it can't
>> allocate all requests, it will return
Alexander Gordeev agord...@redhat.com writes:
On Tue, Feb 04, 2014 at 08:32:12PM +0200, Kalle Valo wrote:
Alexander Gordeev agord...@redhat.com writes:
I don't understand how this is superfluous. When I read the
documentation for pci_enable_msi_block() it states that if it can't
allocate
On Wed, Feb 05, 2014 at 10:21:28AM +0200, Kalle Valo wrote:
Is it ok for me to take these patches to my ath.git tree or would you
prefer to route them some other way?
Yeah, Bjorn has indicated he would pull it to his tree.
I get it you are fine with 2/3 and 3/3?
--
Regards,
Alexander Gordeev
Alexander Gordeev agord...@redhat.com writes:
On Wed, Feb 05, 2014 at 10:21:28AM +0200, Kalle Valo wrote:
Is it ok for me to take these patches to my ath.git tree or would you
prefer to route them some other way?
Yeah, Bjorn has indicated he would pull it to his tree.
Ok, I'll drop these
On Tue, Feb 04, 2014 at 08:32:12PM +0200, Kalle Valo wrote:
> Alexander Gordeev writes:
>
> > Signed-off-by: Alexander Gordeev
> > ---
> > drivers/net/wireless/ath/ath10k/pci.c |2 --
> > 1 files changed, 0 insertions(+), 2 deletions(-)
> >
> > diff --git
Alexander Gordeev writes:
> Signed-off-by: Alexander Gordeev
> ---
> drivers/net/wireless/ath/ath10k/pci.c |2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/pci.c
> b/drivers/net/wireless/ath/ath10k/pci.c
> index 29fd197..6525e1f
Alexander Gordeev agord...@redhat.com writes:
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/net/wireless/ath/ath10k/pci.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c
On Tue, Feb 04, 2014 at 08:32:12PM +0200, Kalle Valo wrote:
Alexander Gordeev agord...@redhat.com writes:
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/net/wireless/ath/ath10k/pci.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git
Signed-off-by: Alexander Gordeev
---
drivers/net/wireless/ath/ath10k/pci.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c
b/drivers/net/wireless/ath/ath10k/pci.c
index 29fd197..6525e1f 100644
---
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/net/wireless/ath/ath10k/pci.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c
b/drivers/net/wireless/ath/ath10k/pci.c
index 29fd197..6525e1f 100644
---
28 matches
Mail list logo
