From: Felipe Balbi <balbi@ti.com>
To: David Miller <davem@davemloft.net>
Cc: balbi@ti.com, mugunthanvnm@ti.com, yegorslists@googlemail.com,
linux-omap@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] net: cpsw: fix hangs and improve IRQ handling
Date: Fri, 2 Jan 2015 15:53:35 -0600 [thread overview]
Message-ID: <20150102215335.GI4920@saruman> (raw)
In-Reply-To: <20150102.164536.1906626949656646358.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, Jan 02, 2015 at 04:45:36PM -0500, David Miller wrote:
> From: Felipe Balbi <balbi@ti.com>
> Date: Fri, 2 Jan 2015 12:10:24 -0600
>
> > In any case, patch 1 should go in during the -rc an get backported
> > all the way back to v3.9, while the other patches can (should) be
> > delayed for v3.20 merge window.
>
> If that's what you want, the way you submitted these changes it not
> the correct way to do it.
>
> You should instead submit patch #1 all by itself, correctly targetting
> 'net'.
>
> Then, after the next time I merge 'net' into 'net-next', you can submit
> the rest of the changes.
then take patch 1 and I'll resend the other in a couple weeks, no
problem.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <balbi@ti.com>, <mugunthanvnm@ti.com>,
<yegorslists@googlemail.com>, <linux-omap@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH 0/4] net: cpsw: fix hangs and improve IRQ handling
Date: Fri, 2 Jan 2015 15:53:35 -0600 [thread overview]
Message-ID: <20150102215335.GI4920@saruman> (raw)
In-Reply-To: <20150102.164536.1906626949656646358.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, Jan 02, 2015 at 04:45:36PM -0500, David Miller wrote:
> From: Felipe Balbi <balbi@ti.com>
> Date: Fri, 2 Jan 2015 12:10:24 -0600
>
> > In any case, patch 1 should go in during the -rc an get backported
> > all the way back to v3.9, while the other patches can (should) be
> > delayed for v3.20 merge window.
>
> If that's what you want, the way you submitted these changes it not
> the correct way to do it.
>
> You should instead submit patch #1 all by itself, correctly targetting
> 'net'.
>
> Then, after the next time I merge 'net' into 'net-next', you can submit
> the rest of the changes.
then take patch 1 and I'll resend the other in a couple weeks, no
problem.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-02 21:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 18:10 [PATCH 0/4] net: cpsw: fix hangs and improve IRQ handling Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 1/4] net: ethernet: cpsw: fix hangs with interrupts Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 2/4] net: ethernet: cpsw: unroll IRQ request loop Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 3/4] net: ethernet: cpsw: split out IRQ handler Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
[not found] ` <CAA93jw7qyZjdHGKXjiBhiYp4BWBFrUFM6FF-Lzc0i7eOnM6cNg@mail.gmail.com>
2015-01-02 18:55 ` Felipe Balbi
2015-01-02 18:55 ` Felipe Balbi
[not found] ` <CAA93jw7=aFM3yQLO+vtN4uHW2gMnfNaY=BdbA+b0WYq-0+gSYQ@mail.gmail.com>
2015-01-02 19:03 ` Felipe Balbi
2015-01-02 19:03 ` Felipe Balbi
2015-01-02 22:56 ` Dave Taht
2015-01-03 3:02 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 4/4] net: ethernet: cpsw: don't requests IRQs we don't use Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 21:45 ` [PATCH 0/4] net: cpsw: fix hangs and improve IRQ handling David Miller
2015-01-02 21:53 ` Felipe Balbi [this message]
2015-01-02 21:53 ` Felipe Balbi
2015-01-02 22:04 ` 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=20150102215335.GI4920@saruman \
--to=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=yegorslists@googlemail.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.