From: David Miller <davem@davemloft.net>
To: dan.j.williams@intel.com
Cc: herbert@gondor.apana.org.au, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
hskinnemoen@atmel.com, maciej.sosnowski@intel.com,
g.liakhovetski@gmx.de, sfr@canb.auug.org.au,
netdev@vger.kernel.org, s.hauer@pengutronix.de
Subject: Re: [GIT PULL, resend] async_tx/dmaengine update for 2.6.29
Date: Mon, 12 Jan 2009 13:16:32 -0800 (PST) [thread overview]
Message-ID: <20090112.131632.119282940.davem@davemloft.net> (raw)
In-Reply-To: <e9c3a7c20901120945r2728e6d3oc9237249d748f8dd@mail.gmail.com>
From: "Dan Williams" <dan.j.williams@intel.com>
Date: Mon, 12 Jan 2009 10:45:02 -0700
> On Mon, Jan 12, 2009 at 5:15 AM, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> > Dan Williams <dan.j.williams@intel.com> wrote:
> >>
> >> net/core/dev.c | 149 +------
> >> net/ipv4/tcp.c | 5 +-
> >> net/ipv4/tcp_input.c | 2 +-
> >> net/ipv4/tcp_ipv4.c | 2 +-
> >> net/ipv6/tcp_ipv6.c | 2 +-
> >
> > Wouldn't it be better for these changes to go through the net
> > tree?
> >
>
> It was awkward to separate the reformatting of the core api from its
> users. In this exceptional case these changes were limited to areas
> inside #ifdef CONFIG_DMA_ENGINE/CONFIG_NET_DMA.
>
> In general, Maciej and I send purely incremental patches through the
> net tree [1].
Yes, I think in this case it didn't make much sense to send
the changes via the net tree.
next prev parent reply other threads:[~2009-01-12 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:15 [GIT PULL, resend] async_tx/dmaengine update for 2.6.29 Herbert Xu
2009-01-12 17:45 ` Dan Williams
2009-01-12 21:16 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-09 15:16 Dan Williams
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=20090112.131632.119282940.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=herbert@gondor.apana.org.au \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).