diff for duplicates of <1478795309.2603.55.camel@synopsys.com> diff --git a/a/1.txt b/N1/1.txt index f1abdeb..ec39b31 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,8 +1,8 @@ -On Tue, 2016-11-08@15:36 +0200, Andy Shevchenko wrote: -> On Tue, 2016-11-08@12:22 +0000, Eugeniy Paltsev wrote: +On Tue, 2016-11-08 at 15:36 +0200, Andy Shevchenko wrote: +> On Tue, 2016-11-08 at 12:22 +0000, Eugeniy Paltsev wrote: > > -> > On Mon, 2016-11-07@15:55 +0200, Andy Shevchenko wrote: -> ? +> > On Mon, 2016-11-07 at 15:55 +0200, Andy Shevchenko wrote: +> > > > > > > > > > @@ -17,36 +17,36 @@ On Tue, 2016-11-08@15:36 +0200, Andy Shevchenko wrote: > > > copied > > > from > > > platform data. -> > See?comment below. +> > See comment below. > > > > > -> > > ? +> > > > > > > -> > > > ? -> > > > ???* @is_nollp: The device channels does not support multi +> > > > +> > > > * @is_nollp: The device channels does not support multi > > > > block > > > > transfers. -> > > > ???* @chan_allocation_order: Allocate channels starting from 0 +> > > > * @chan_allocation_order: Allocate channels starting from 0 > > > > or > > > > 7 -> > > > ???* @chan_priority: Set channel priority increasing from 0 to +> > > > * @chan_priority: Set channel priority increasing from 0 to > > > > 7 > > > > or > > > > 7 > > > > to 0. > > > > @@ -52,6 +55,7 @@ struct dw_dma_platform_data { -> > > > ?? unsigned int nr_channels; -> > > > ?? bool is_private; -> > > > ?? bool is_memcpy; -> > > > ? +> > > > unsigned int nr_channels; +> > > > bool is_private; +> > > > bool is_memcpy; +> > > > > > > > + bool only_quirks_used; -> > > Perhaps add if at the end of quirk list and name just? -> > > ? +> > > Perhaps add if at the end of quirk list and name just +> > > > > > > -> > > > ? -> > > > ?? bool is_nollp; +> > > > +> > > > bool is_nollp; > > > ...here -> > > ? +> > > > > > bool use_quirks; > What do think about shorten name? > @@ -56,7 +56,7 @@ variable. You can suggest your ideas if you want. > > > > I don't treat "is_nollp" as quirks like "is_private" or > > "is_memcpy". -> > It is like general pdata field: we can easily?read it from +> > It is like general pdata field: we can easily read it from > > autoconfig > > registers (and we don't have any problem with that) in case of > > pdata/device-tree absence (as opposed to quirks like "is_private" @@ -89,4 +89,4 @@ Please correct me if I'm wrong. So, in my opinion, "is_nollp" should be used as regular pdata field. -- -?Paltsev Eugeniy + Paltsev Eugeniy diff --git a/a/content_digest b/N1/content_digest index 0dafa9a..07daad8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,17 +3,24 @@ "ref\01478526908.5295.67.camel@linux.intel.com\0" "ref\01478607771.2603.31.camel@synopsys.com\0" "ref\01478612190.5295.92.camel@linux.intel.com\0" - "From\0Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)\0" - "Subject\0[PATCH v3 0/3] dmaengine: DW DMAC: split pdata to hardware properties\0" + "From\0Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>\0" + "Subject\0Re: [PATCH v3 0/3] dmaengine: DW DMAC: split pdata to hardware properties\0" "Date\0Thu, 10 Nov 2016 16:28:29 +0000\0" - "To\0linux-snps-arc@lists.infradead.org\0" + "To\0andriy.shevchenko@linux.intel.com <andriy.shevchenko@linux.intel.com>\0" + "Cc\0dan.j.williams@intel.com <dan.j.williams@intel.com>" + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + Eugeniy.Paltsev@synopsys.com <Eugeniy.Paltsev@synopsys.com> + dmaengine@vger.kernel.org <dmaengine@vger.kernel.org> + vinod.koul@intel.com <vinod.koul@intel.com> + vireshk@kernel.org <vireshk@kernel.org> + " linux-snps-arc@lists.infradead.org <linux-snps-arc@lists.infradead.org>\0" "\00:1\0" "b\0" - "On Tue, 2016-11-08@15:36 +0200, Andy Shevchenko wrote:\n" - "> On Tue, 2016-11-08@12:22 +0000, Eugeniy Paltsev wrote:\n" + "On Tue, 2016-11-08 at 15:36 +0200, Andy Shevchenko wrote:\n" + "> On Tue, 2016-11-08 at 12:22 +0000, Eugeniy Paltsev wrote:\n" "> > \n" - "> > On Mon, 2016-11-07@15:55 +0200, Andy Shevchenko wrote:\n" - "> ?\n" + "> > On Mon, 2016-11-07 at 15:55 +0200, Andy Shevchenko wrote:\n" + "> \302\240\n" "> > \n" "> > > \n" "> > > > \n" @@ -28,36 +35,36 @@ "> > > copied\n" "> > > from\n" "> > > platform data.\n" - "> > See?comment below.\n" + "> > See\302\240comment below.\n" "> > \n" "> > > \n" - "> > > ?\n" + "> > > \302\240\n" "> > > > \n" - "> > > > ?\n" - "> > > > ???* @is_nollp: The device channels does not support multi\n" + "> > > > \302\240\n" + "> > > > \302\240\302\240\302\240* @is_nollp: The device channels does not support multi\n" "> > > > block\n" "> > > > transfers.\n" - "> > > > ???* @chan_allocation_order: Allocate channels starting from 0\n" + "> > > > \302\240\302\240\302\240* @chan_allocation_order: Allocate channels starting from 0\n" "> > > > or\n" "> > > > 7\n" - "> > > > ???* @chan_priority: Set channel priority increasing from 0 to\n" + "> > > > \302\240\302\240\302\240* @chan_priority: Set channel priority increasing from 0 to\n" "> > > > 7\n" "> > > > or\n" "> > > > 7\n" "> > > > to 0.\n" "> > > > @@ -52,6 +55,7 @@ struct dw_dma_platform_data {\n" - "> > > > ??\tunsigned int\tnr_channels;\n" - "> > > > ??\tbool\t\tis_private;\n" - "> > > > ??\tbool\t\tis_memcpy;\n" - "> > > > ?\n" + "> > > > \302\240\302\240\tunsigned int\tnr_channels;\n" + "> > > > \302\240\302\240\tbool\t\tis_private;\n" + "> > > > \302\240\302\240\tbool\t\tis_memcpy;\n" + "> > > > \302\240\n" "> > > > +\tbool\t\tonly_quirks_used;\n" - "> > > Perhaps add if at the end of quirk list and name just?\n" - "> > > ?\n" + "> > > Perhaps add if at the end of quirk list and name just\302\240\n" + "> > > \302\240\n" "> > > > \n" - "> > > > ?\n" - "> > > > ??\tbool\t\tis_nollp;\n" + "> > > > \302\240\n" + "> > > > \302\240\302\240\tbool\t\tis_nollp;\n" "> > > ...here\n" - "> > > ?\n" + "> > > \302\240\n" "> > > bool use_quirks;\n" "> What do think about shorten name?\n" "> \n" @@ -67,7 +74,7 @@ "> > \n" "> > I don't treat \"is_nollp\" as quirks like \"is_private\" or\n" "> > \"is_memcpy\".\n" - "> > It is like general pdata field: we can easily?read it from\n" + "> > It is like general pdata field: we can easily\302\240read it from\n" "> > autoconfig\n" "> > registers (and we don't have any problem with that) in case of\n" "> > pdata/device-tree absence (as opposed to quirks like \"is_private\"\n" @@ -100,6 +107,6 @@ "\n" "So, in my opinion, \"is_nollp\" should be used as regular pdata field.\n" "-- \n" - ?Paltsev Eugeniy + "\302\240Paltsev Eugeniy" -7b8adf97d16a28f2c88d97bf3a3b8dc2d65152e7e549298c90abf742ff4ada13 +45b2f7de14b4275014ddf862b3a1311f4be88b8451196e646598b3ba584f4b5e
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.