Re: [PATCH v2] userdiff: Add a builtin pattern for dts files

2019-08-19 Thread Johannes Sixt
Am 19.08.19 um 22:44 schrieb Stephen Boyd: > Quoting Johannes Sixt (2019-08-19 11:40:47) >> Am 17.08.19 um 00:56 schrieb Stephen Boyd: >>> diff --git a/t/t4018/dts-labels b/t/t4018/dts-labels >>> new file mode 100644 >>> index ..27cd4921cfb6 >>> --- /dev/null >>> +++ b/t/t4018/dts-label

Re: [PATCH v2] userdiff: Add a builtin pattern for dts files

2019-08-19 Thread Stephen Boyd
Quoting Johannes Sixt (2019-08-19 11:40:47) > Am 17.08.19 um 00:56 schrieb Stephen Boyd: > > The Linux kernel receives many patches to the devicetree files each > > release. The hunk header for those patches typically show nothing, > > making it difficult to figure out what node is being modified w

Re: [PATCH v2] userdiff: Add a builtin pattern for dts files

2019-08-19 Thread Johannes Sixt
Am 17.08.19 um 00:56 schrieb Stephen Boyd: > The Linux kernel receives many patches to the devicetree files each > release. The hunk header for those patches typically show nothing, > making it difficult to figure out what node is being modified without > applying the patch or opening the file and

Re: [PATCH v2] userdiff: Add a builtin pattern for dts files

2019-08-17 Thread Alban Gruin
Hi Stephen, Le 17/08/2019 à 00:56, Stephen Boyd a écrit : > The Linux kernel receives many patches to the devicetree files each > release. The hunk header for those patches typically show nothing, > making it difficult to figure out what node is being modified without > applying the patch or openi

Re: [PATCH v2] userdiff: Add a builtin pattern for dts files

2019-08-16 Thread Frank Rowand
+Frank (me) On 8/16/19 3:56 PM, Stephen Boyd wrote: > The Linux kernel receives many patches to the devicetree files each > release. The hunk header for those patches typically show nothing, > making it difficult to figure out what node is being modified without > applying the patch or opening the

[PATCH v2] userdiff: Add a builtin pattern for dts files

2019-08-16 Thread Stephen Boyd
The Linux kernel receives many patches to the devicetree files each release. The hunk header for those patches typically show nothing, making it difficult to figure out what node is being modified without applying the patch or opening the file and seeking to the context. Let's add a builtin 'dts' p