1 |
s/you are commented/you commented/ |
2 |
|
3 |
:) |
4 |
|
5 |
On 6 August 2016 at 12:25, Natanael Olaiz <nolaiz@×××××.com> wrote: |
6 |
|
7 |
> David, |
8 |
> |
9 |
> Thank you for your patch. It was a good example to answer my question. |
10 |
> |
11 |
> But about the patch itself, I see that you are commented the code for |
12 |
> radix_tree_empty(...). In my patch I renamed it and it only usage instead, |
13 |
> so I'm sure it's calling the same code. I don't know the expected |
14 |
> compatibility with the kernel function implementation... But without |
15 |
> knowing the specific code for neither the nvidia driver nor the kernel, I |
16 |
> think the rename is safer... |
17 |
> |
18 |
> |
19 |
> Best regards, |
20 |
> Natanael |
21 |
> |
22 |
> |
23 |
> On 6 August 2016 at 04:50, David Haller <gentoo@×××××××.de> wrote: |
24 |
> |
25 |
>> Hello, |
26 |
>> |
27 |
>> On Fri, 05 Aug 2016, Mike Gilbert wrote: |
28 |
>> >On Fri, Aug 5, 2016 at 3:10 PM, Natanael Olaiz <nolaiz@×××××.com> wrote: |
29 |
>> >> I know that. But the patch should be applied *only* for versions of |
30 |
>> kernels |
31 |
>> >> 4.7+. So, I'm asking how is the policy for that. |
32 |
>> > |
33 |
>> >If you're asking for policy: The Gentoo packaging policy is not to do |
34 |
>> >conditional patching. Instead, modify the patch so that the resulting |
35 |
>> >code works for both cases. This can generally be accomplished via |
36 |
>> >pre-processor macros. |
37 |
>> |
38 |
>> My patch does it like that. See |
39 |
>> https://archives.gentoo.org/gentoo-user/message/baa36d14d8c |
40 |
>> dbf58404267ee2ffd34ea |
41 |
>> Just dumping the attached patch into |
42 |
>> /etc/portage/patches/x11-drivers/nvidia-drivers-367.35/ |
43 |
>> (and making it readable for the portage user) is sufficient. |
44 |
>> |
45 |
>> HTH, |
46 |
>> -dnh |
47 |
>> |
48 |
>> -- |
49 |
>> Every feature is a bug, unless it can be turned off. -- Karl Heuer |
50 |
> |
51 |
> |
52 |
> |