From: David Miller <davem@davemloft.net>
To: christophe.jaillet@wanadoo.fr
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/3] net: stmmac: Fixes and cleanups in 'alloc_dma_[rt]x_desc_resources()'
Date: Tue, 11 Jul 2017 13:34:11 -0700 (PDT) [thread overview]
Message-ID: <20170711.133411.864910706448052867.davem@davemloft.net> (raw)
In-Reply-To: <cover.1499499451.git.christophe.jaillet@wanadoo.fr>
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date: Sat, 8 Jul 2017 09:46:12 +0200
> These patchs are all related to 'alloc_dma_[rt]x_desc_resources()' functions.
>
> The 2 first fix an error path where some resources are leaking. I've
> separated them into 2 patches because the issues have been introduced by
> 2 deferent commits.
>
> The 3rd patch is just a clean-up.
Series applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: christophe.jaillet@wanadoo.fr
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/3] net: stmmac: Fixes and cleanups in 'alloc_dma_[rt]x_desc_resources()'
Date: Tue, 11 Jul 2017 20:34:11 +0000 [thread overview]
Message-ID: <20170711.133411.864910706448052867.davem@davemloft.net> (raw)
In-Reply-To: <cover.1499499451.git.christophe.jaillet@wanadoo.fr>
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date: Sat, 8 Jul 2017 09:46:12 +0200
> These patchs are all related to 'alloc_dma_[rt]x_desc_resources()' functions.
>
> The 2 first fix an error path where some resources are leaking. I've
> separated them into 2 patches because the issues have been introduced by
> 2 deferent commits.
>
> The 3rd patch is just a clean-up.
Series applied, thanks.
next prev parent reply other threads:[~2017-07-11 20:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 7:46 [PATCH 0/3] net: stmmac: Fixes and cleanups in 'alloc_dma_[rt]x_desc_resources()' Christophe JAILLET
2017-07-08 7:46 ` Christophe JAILLET
2017-07-08 7:46 ` [PATCH 1/3] net: stmmac: Fix error handling path in 'alloc_dma_rx_desc_resources()' Christophe JAILLET
2017-07-08 7:46 ` Christophe JAILLET
2017-07-10 6:21 ` Giuseppe CAVALLARO
2017-07-10 6:21 ` Giuseppe CAVALLARO
2017-07-08 7:46 ` [PATCH 2/3] net: stmmac: Fix error handling path in 'alloc_dma_tx_desc_resources()' Christophe JAILLET
2017-07-08 7:46 ` Christophe JAILLET
2017-07-10 6:22 ` Giuseppe CAVALLARO
2017-07-10 6:22 ` Giuseppe CAVALLARO
2017-07-08 7:46 ` [PATCH 3/3] net: stmmac: Make 'alloc_dma_[rt]x_desc_resources()' look even closer Christophe JAILLET
2017-07-08 7:46 ` Christophe JAILLET
2017-07-10 6:22 ` Giuseppe CAVALLARO
2017-07-10 6:22 ` Giuseppe CAVALLARO
2017-07-11 20:34 ` David Miller [this message]
2017-07-11 20:34 ` [PATCH 0/3] net: stmmac: Fixes and cleanups in 'alloc_dma_[rt]x_desc_resources()' 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=20170711.133411.864910706448052867.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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.