From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v6] testpmd: Add port hotplug support Date: Mon, 02 Feb 2015 12:57:39 +0100 Message-ID: <1688512.MY7Nexz1BF@xps13> References: <1421664027-17971-9-git-send-email-mukawa@igel.co.jp> <1422763322-13742-16-git-send-email-mukawa@igel.co.jp> <8CEF83825BEC744B83065625E567D7C2049DCAD2@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: "Iremonger, Bernard" Return-path: In-Reply-To: <8CEF83825BEC744B83065625E567D7C2049DCAD2-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2015-02-02 11:33, Iremonger, Bernard: > From: Tetsuya Mukawa [mailto:mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org] > > --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst > > +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst > Hi Tetsuya, > > The doc changes should be in separate commit using the "doc: explaination" commit line. I agree that new docs should be in a separate commit. Though when updating some code (like here), it's a good idea to update the doc in the same commit. Then the change is atomic. If you want to figure which patches are updating the doc, it should be possible to have a filter on "+++ b/doc/". -- Thomas