Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, Feb 12, 2017 at 07:56:41PM +0100, Thomas Gleixner wrote: [ ... ] > I've applied it already and fixed up the subject/changelog. You should have > mail from tip-bot ... For the record, I did not receive the mails from the tip-bot when the patches from the PR were applied. -- Daniel

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, Feb 12, 2017 at 07:56:41PM +0100, Thomas Gleixner wrote: [ ... ] > I've applied it already and fixed up the subject/changelog. You should have > mail from tip-bot ... For the record, I did not receive the mails from the tip-bot when the patches from the PR were applied. -- Daniel

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Mon, Feb 13, 2017 at 12:26 AM, Thomas Gleixner wrote: > On Sun, 12 Feb 2017, Bhumika Goyal wrote: > >> On Sun, Feb 12, 2017 at 2:01 AM, Ard Biesheuvel >> wrote: >> > On 11 February 2017 at 19:20, Bhumika Goyal wrote: >> >>

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Mon, Feb 13, 2017 at 12:26 AM, Thomas Gleixner wrote: > On Sun, 12 Feb 2017, Bhumika Goyal wrote: > >> On Sun, Feb 12, 2017 at 2:01 AM, Ard Biesheuvel >> wrote: >> > On 11 February 2017 at 19:20, Bhumika Goyal wrote: >> >> The object cyclecounter of type cyclecounter is not getting modified

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, 12 Feb 2017, Bhumika Goyal wrote: > On Sun, Feb 12, 2017 at 2:01 AM, Ard Biesheuvel > wrote: > > On 11 February 2017 at 19:20, Bhumika Goyal wrote: > >> The object cyclecounter of type cyclecounter is not getting modified > >> after getting

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, 12 Feb 2017, Bhumika Goyal wrote: > On Sun, Feb 12, 2017 at 2:01 AM, Ard Biesheuvel > wrote: > > On 11 February 2017 at 19:20, Bhumika Goyal wrote: > >> The object cyclecounter of type cyclecounter is not getting modified > >> after getting initialized by arch_counter_register. Apart

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, Feb 12, 2017 at 2:05 AM, Thomas Gleixner wrote: > On Sun, 12 Feb 2017, Bhumika Goyal wrote: > > Please be more careful with your subject line. The prefix for this is > definitely not 'clocksource'. git log would have told you the proper one: > >

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, Feb 12, 2017 at 2:05 AM, Thomas Gleixner wrote: > On Sun, 12 Feb 2017, Bhumika Goyal wrote: > > Please be more careful with your subject line. The prefix for this is > definitely not 'clocksource'. git log would have told you the proper one: > > clocksource/drivers/arm_arch_timer > >

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, Feb 12, 2017 at 2:01 AM, Ard Biesheuvel wrote: > On 11 February 2017 at 19:20, Bhumika Goyal wrote: >> The object cyclecounter of type cyclecounter is not getting modified >> after getting initialized by arch_counter_register. Apart from >>

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, Feb 12, 2017 at 2:01 AM, Ard Biesheuvel wrote: > On 11 February 2017 at 19:20, Bhumika Goyal wrote: >> The object cyclecounter of type cyclecounter is not getting modified >> after getting initialized by arch_counter_register. Apart from >> initialization in arch_counter_register it is

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sat, 11 Feb 2017, Ard Biesheuvel wrote: > On 11 February 2017 at 19:20, Bhumika Goyal wrote: > > The object cyclecounter of type cyclecounter is not getting modified > > after getting initialized by arch_counter_register. Apart from > > initialization in

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sat, 11 Feb 2017, Ard Biesheuvel wrote: > On 11 February 2017 at 19:20, Bhumika Goyal wrote: > > The object cyclecounter of type cyclecounter is not getting modified > > after getting initialized by arch_counter_register. Apart from > > initialization in arch_counter_register it is also

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, 12 Feb 2017, Bhumika Goyal wrote: Please be more careful with your subject line. The prefix for this is definitely not 'clocksource'. git log would have told you the proper one: clocksource/drivers/arm_arch_timer 'clocksource' is the general subsystem and used for system wide changes or

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On Sun, 12 Feb 2017, Bhumika Goyal wrote: Please be more careful with your subject line. The prefix for this is definitely not 'clocksource'. git log would have told you the proper one: clocksource/drivers/arm_arch_timer 'clocksource' is the general subsystem and used for system wide changes or

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On 11 February 2017 at 19:20, Bhumika Goyal wrote: > The object cyclecounter of type cyclecounter is not getting modified > after getting initialized by arch_counter_register. Apart from > initialization in arch_counter_register it is also passed as an argument > to the

Re: [PATCH] clocksource: add __ro_after_init to cyclecounter

On 11 February 2017 at 19:20, Bhumika Goyal wrote: > The object cyclecounter of type cyclecounter is not getting modified > after getting initialized by arch_counter_register. Apart from > initialization in arch_counter_register it is also passed as an argument > to the function timecounter_init

[PATCH] clocksource: add __ro_after_init to cyclecounter

The object cyclecounter of type cyclecounter is not getting modified after getting initialized by arch_counter_register. Apart from initialization in arch_counter_register it is also passed as an argument to the function timecounter_init but this argument is of type const. Therefore, add

[PATCH] clocksource: add __ro_after_init to cyclecounter

The object cyclecounter of type cyclecounter is not getting modified after getting initialized by arch_counter_register. Apart from initialization in arch_counter_register it is also passed as an argument to the function timecounter_init but this argument is of type const. Therefore, add