[no subject]

[Sistem Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Venkat Subbiah]

Sup Linux


http://www.imr-asso.org/wp-content/uploads/innovation.php?corn=pks2ea81htmcx01ew



Venkat

[no subject]

[Venkat Subbiah]

Sup Linux


http://www.imr-asso.org/wp-content/uploads/innovation.php?corn=pks2ea81htmcx01ew



Venkat

[no subject]

[Andrew Worsley]

Hi, this extends the one wire master DS2482 driver to support other interfacing
modes and adds a slave one wire DS28E05 EEPROM driver. This allows the one
wire master DS2482 driver to support the OverDrive interface mode which is
required for it to talk to the DS28E05 slave chip.

These patches are against the recent 4.13.0-rc6 mainline kernel and compile
against it. The code was tested against the recent Debian stable 4.9 kernel.
The code did require some changes between the two kernels to compile but are
functionally the same.

Hopefully it is useful for some other people wanting to use these or similar
chips.

Thanks

Andrew Worsley

[no subject]

[Andrew Worsley]

Hi, this extends the one wire master DS2482 driver to support other interfacing
modes and adds a slave one wire DS28E05 EEPROM driver. This allows the one
wire master DS2482 driver to support the OverDrive interface mode which is
required for it to talk to the DS28E05 slave chip.

These patches are against the recent 4.13.0-rc6 mainline kernel and compile
against it. The code was tested against the recent Debian stable 4.9 kernel.
The code did require some changes between the two kernels to compile but are
functionally the same.

Hopefully it is useful for some other people wanting to use these or similar
chips.

Thanks

Andrew Worsley

[no subject]

[timothy.sodini]

306027330035843.doc
Description: MS-Word document

[no subject]

[timothy.sodini]

306027330035843.doc
Description: MS-Word document

[no subject]

[timothy.sodini]

306027330035843.doc
Description: MS-Word document

[no subject]

[timothy.sodini]

306027330035843.doc
Description: MS-Word document

[no subject]

[Mrs Wang Ling]

Hello!
I am Mrs Wang Ling, I work at Lloyds TSB pacific LTD, I have a business
proposal, contact me so i will tell you all about this proposal .

Kind Regards
Mrs Wang Ling

[no subject]

[Mrs Wang Ling]

Hello!
I am Mrs Wang Ling, I work at Lloyds TSB pacific LTD, I have a business
proposal, contact me so i will tell you all about this proposal .

Kind Regards
Mrs Wang Ling

[no subject]

[Nicholas Piggin]

Date: Sun, 20 Aug 2017 13:16:16 +1000
Subject: [PATCH] timers: Fix excessive granularity of new timers after a nohz
 idle

When a timer base is idle, it is forwarded when a new timer is added
to ensure that granularity does not become excessive. When not idle,
the timer tick is expected to increment the base.

However there are several problems:

- If an existing timer is modified, the base is forwarded only after
  the index is calculated.

- The base is not forwarded by add_timer_on.

- There is a window after a timer is restarted from a nohz ide, after
  it is marked not-idle and before the timer tick on this CPU, where a
  timer may be added but the ancient base does not get forwarded.

These result in excessive granularity (a 1 jiffy timeout can blow out
to 100s of jiffies), which cause the rcu lockup detector to trigger,
among other things.

Fix this by keeping track of whether the timer base has been idle
since it was last run or forwarded, and if so then forward it before
adding a new timer.

There is still a problem where the mod_timer optimization where it's
modified with the same expiry time can result in excessive granularity
relative to the new shorter interval. That is not addressed by this
patch because checking base->was_idle would increase overhead and it's
a rather special case (you could reason that the caller should not
expect change in absolute expiry time due to such an operation). So
that is noted as a comment.

As well as fixing the visible RCU softlockup failures, I tested an
idle system (with no lockup watchdogs running) and traced all
non-deferrable timer expiries for 1000s, and analysed wakeup latency
relative to requested latency.  1.0 means we slept for as many jiffies
as requested, 2.0 means we slept 2x the time (this suffers jiffies
round-up skew at low absolute times):

 max avg  std
upstream   506.01.20 4.68
patched  2.01.08 0.15

This was noticed due to the lockup detector Kconfig changes dropping it
out of people's .configs. When the lockup detectors are enabled, no CPU
can go idle for longer than 4 seconds, which limits the granularity
errors. Sub-optimal timer behaviour is observable on a smaller scale:

 max avg  std
upstream 9.01.05 0.19
patched  2.01.04 0.11

Tested-by: David Miller <da...@davemloft.net>
Signed-off-by: Nicholas Piggin <npig...@gmail.com>
---

Hi Andrew,

I would have preferred to get comments from the timer maintainers, but
they've been busy or away for the past copule of weeks. Perhaps you
would consider carrying it until then?

Thanks,
Nick

 kernel/time/timer.c | 44 
 1 file changed, 36 insertions(+), 8 deletions(-)

diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index 8f5d1bf18854..dd7be9fe6839 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -203,6 +203,7 @@ struct timer_base {
boolmigration_enabled;
boolnohz_active;
boolis_idle;
+   boolwas_idle; /* was it idle since last run/fwded */
DECLARE_BITMAP(pending_map, WHEEL_SIZE);
struct hlist_head   vectors[WHEEL_SIZE];
 } cacheline_aligned;
@@ -856,13 +857,19 @@ get_target_base(struct timer_base *base, unsigned tflags)
 
 static inline void forward_timer_base(struct timer_base *base)
 {
-   unsigned long jnow = READ_ONCE(jiffies);
+   unsigned long jnow;
 
/*
-* We only forward the base when it's idle and we have a delta between
-* base clock and jiffies.
+* We only forward the base when we are idle or have just come out
+* of idle (was_idle logic), and have a delta between base clock
+* and jiffies. In the common case, run_timers will take care of it.
 */
-   if (!base->is_idle || (long) (jnow - base->clk) < 2)
+   if (likely(!base->was_idle))
+   return;
+
+   jnow = READ_ONCE(jiffies);
+   base->was_idle = base->is_idle;
+   if ((long)(jnow - base->clk) < 2)
return;
 
/*
@@ -938,6 +945,13 @@ __mod_timer(struct timer_list *timer, unsigned long 
expires, bool pending_only)
 * same array bucket then just return:
 */
if (timer_pending(timer)) {
+   /*
+* The downside of this optimization is that it can result in
+* larger granularity than you would get from adding a new
+* timer with this expiry. Would a timer flag for networking
+* be appropriate, then we can try to keep expiry of general
+* timers within ~1/8th of their interval?
+*/
if (timer->expires == expires)
return 1;
 
@@ -948,6 +962,7 @@ __mod_timer(struct timer_list *timer, unsigned long 
expires, bool pending_only

[no subject]

[Nicholas Piggin]

Date: Sun, 20 Aug 2017 13:16:16 +1000
Subject: [PATCH] timers: Fix excessive granularity of new timers after a nohz
 idle

When a timer base is idle, it is forwarded when a new timer is added
to ensure that granularity does not become excessive. When not idle,
the timer tick is expected to increment the base.

However there are several problems:

- If an existing timer is modified, the base is forwarded only after
  the index is calculated.

- The base is not forwarded by add_timer_on.

- There is a window after a timer is restarted from a nohz ide, after
  it is marked not-idle and before the timer tick on this CPU, where a
  timer may be added but the ancient base does not get forwarded.

These result in excessive granularity (a 1 jiffy timeout can blow out
to 100s of jiffies), which cause the rcu lockup detector to trigger,
among other things.

Fix this by keeping track of whether the timer base has been idle
since it was last run or forwarded, and if so then forward it before
adding a new timer.

There is still a problem where the mod_timer optimization where it's
modified with the same expiry time can result in excessive granularity
relative to the new shorter interval. That is not addressed by this
patch because checking base->was_idle would increase overhead and it's
a rather special case (you could reason that the caller should not
expect change in absolute expiry time due to such an operation). So
that is noted as a comment.

As well as fixing the visible RCU softlockup failures, I tested an
idle system (with no lockup watchdogs running) and traced all
non-deferrable timer expiries for 1000s, and analysed wakeup latency
relative to requested latency.  1.0 means we slept for as many jiffies
as requested, 2.0 means we slept 2x the time (this suffers jiffies
round-up skew at low absolute times):

 max avg  std
upstream   506.01.20 4.68
patched  2.01.08 0.15

This was noticed due to the lockup detector Kconfig changes dropping it
out of people's .configs. When the lockup detectors are enabled, no CPU
can go idle for longer than 4 seconds, which limits the granularity
errors. Sub-optimal timer behaviour is observable on a smaller scale:

 max avg  std
upstream 9.01.05 0.19
patched  2.01.04 0.11

Tested-by: David Miller 
Signed-off-by: Nicholas Piggin 
---

Hi Andrew,

I would have preferred to get comments from the timer maintainers, but
they've been busy or away for the past copule of weeks. Perhaps you
would consider carrying it until then?

Thanks,
Nick

 kernel/time/timer.c | 44 
 1 file changed, 36 insertions(+), 8 deletions(-)

diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index 8f5d1bf18854..dd7be9fe6839 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -203,6 +203,7 @@ struct timer_base {
boolmigration_enabled;
boolnohz_active;
boolis_idle;
+   boolwas_idle; /* was it idle since last run/fwded */
DECLARE_BITMAP(pending_map, WHEEL_SIZE);
struct hlist_head   vectors[WHEEL_SIZE];
 } cacheline_aligned;
@@ -856,13 +857,19 @@ get_target_base(struct timer_base *base, unsigned tflags)
 
 static inline void forward_timer_base(struct timer_base *base)
 {
-   unsigned long jnow = READ_ONCE(jiffies);
+   unsigned long jnow;
 
/*
-* We only forward the base when it's idle and we have a delta between
-* base clock and jiffies.
+* We only forward the base when we are idle or have just come out
+* of idle (was_idle logic), and have a delta between base clock
+* and jiffies. In the common case, run_timers will take care of it.
 */
-   if (!base->is_idle || (long) (jnow - base->clk) < 2)
+   if (likely(!base->was_idle))
+   return;
+
+   jnow = READ_ONCE(jiffies);
+   base->was_idle = base->is_idle;
+   if ((long)(jnow - base->clk) < 2)
return;
 
/*
@@ -938,6 +945,13 @@ __mod_timer(struct timer_list *timer, unsigned long 
expires, bool pending_only)
 * same array bucket then just return:
 */
if (timer_pending(timer)) {
+   /*
+* The downside of this optimization is that it can result in
+* larger granularity than you would get from adding a new
+* timer with this expiry. Would a timer flag for networking
+* be appropriate, then we can try to keep expiry of general
+* timers within ~1/8th of their interval?
+*/
if (timer->expires == expires)
return 1;
 
@@ -948,6 +962,7 @@ __mod_timer(struct timer_list *timer, unsigned long 
expires, bool pending_only)
 * dequeue/enqueue dance.
  

[no subject]

[Ciprian]

Good evening 

http://www.albit.ro/s2daddr.php?fight=27sfbr9drm6n4




Ciprian

[no subject]

[Ciprian]

Good evening 

http://www.albit.ro/s2daddr.php?fight=27sfbr9drm6n4




Ciprian

[no subject]

[Jagan Teki]

unsubscribe git

[no subject]

[Jagan Teki]

unsubscribe git

[no subject]

[Rajneesh Bhardwaj]

Bcc: 
Subject: Re: [PATCH] platform/x86: intel_pmc_core: Add Package C-states
 residency info
Reply-To: 
In-Reply-To: 
<cahp75vd5wnio-rcebentonywojf2+88fdvqkuv1hzv3cdca...@mail.gmail.com>

On Fri, Aug 18, 2017 at 08:17:32PM +0300, Andy Shevchenko wrote:
> +PeterZ (since I mentioned his name)
> 
> On Fri, Aug 18, 2017 at 5:58 PM, Rajneesh Bhardwaj
> <rajneesh.bhard...@intel.com> wrote:
> > On Fri, Aug 18, 2017 at 03:57:34PM +0300, Andy Shevchenko wrote:
> >> On Fri, Aug 18, 2017 at 3:37 PM, Rajneesh Bhardwaj
> >> <rajneesh.bhard...@intel.com> wrote:
> >> > This patch introduces a new debugfs entry to read current Package C-state
> >> > residency values and, one new kernel API to read the Package C-10 
> >> > residency
> >> > counter.
> >> >
> >> > Package C-state residency MSRs provide useful debug information about 
> >> > system
> >> > idle states. In idle states system must enter deeper Package C-states.
> 
> >> Why this patch is needed?
> >
> > Andy, I'll try to give some background for this.
> >
> > This is needed to enhance the S0ix failure debug capabilities from within
> > the kernel. On ChromeOS we have S0ix failsafe kernel framework that is used
> > to validate S0ix and report the blockers in case of a failure.
> > https://patchwork.kernel.org/patch/9148999/
> 
> (It's not part of upstream)

Sorry i sent an older link. There are fresh attempts to get this into
mainline kernel and looks like there is a traction for it.
https://patchwork.kernel.org/patch/9831229/

Package C-state (PC10) validation is discussed there.

> 
> > So far only intel_pmc_slp_s0_counter_read is called by this framework to
> > check whether the previous attempt to enter S0ix was success or not.
> 
> I harder see even a single user of that API in current kernel. It
> should be unexported and removed I think.
> 
> >  Having
> > another PC10 counter related exported function enhances the S0ix debug since
> > PC10 state is a prerequisite to enter S0ix.
> >
> >> See, we have turbostat and cpupower user space tools which do this
> >> without any additional code to be written in kernel. What prevents
> >> your user space application do the same?
> >>
> >> Moreover, we have events for cstate, I assume perf or something alike
> >> can monitor those counters as well.
> >
> > You're right, perhaps the debugfs is redundant when we have those user space
> > tools but such tools are not available readily for all platforms/distros.
> > Interfaces like /dev/cpu/*/msr that turbostat uses are not available on all
> > the platforms.
> > PMC driver is a debug driver so i thought its better to show Package C-state
> > related info for low power debug here.
> >
> >>
> >> Sorry, NAK.
> >
> > This patch has two parts i.e. exported PC10 API and the debugfs. Based on
> > the above explanation, if the patch is not good as is, please let me know if
> > i should drop the debugfs part and respin a v2 with just the exported API or
> > drop this totally.
> >
> > Thanks for the feedback and thanks for taking time to review!
> 
> Reading above makes me think that entire design of this is misguided.
> Since the most of values are counters they better to be accessed in a
> way how perf does.
> 
> In case you need *in-kernel* facility, do some APIs (if it's not done
> yet) for events drivers first.
> cstate event driver is already in upstream.
> 
> Sorry, NAK for entire patch until it would be blessed by people like Peter Z.
> 
> -- 
> With Best Regards,
> Andy Shevchenko

-- 
Best Regards,
Rajneesh

[no subject]

[Rajneesh Bhardwaj]

Bcc: 
Subject: Re: [PATCH] platform/x86: intel_pmc_core: Add Package C-states
 residency info
Reply-To: 
In-Reply-To: 


On Fri, Aug 18, 2017 at 08:17:32PM +0300, Andy Shevchenko wrote:
> +PeterZ (since I mentioned his name)
> 
> On Fri, Aug 18, 2017 at 5:58 PM, Rajneesh Bhardwaj
>  wrote:
> > On Fri, Aug 18, 2017 at 03:57:34PM +0300, Andy Shevchenko wrote:
> >> On Fri, Aug 18, 2017 at 3:37 PM, Rajneesh Bhardwaj
> >>  wrote:
> >> > This patch introduces a new debugfs entry to read current Package C-state
> >> > residency values and, one new kernel API to read the Package C-10 
> >> > residency
> >> > counter.
> >> >
> >> > Package C-state residency MSRs provide useful debug information about 
> >> > system
> >> > idle states. In idle states system must enter deeper Package C-states.
> 
> >> Why this patch is needed?
> >
> > Andy, I'll try to give some background for this.
> >
> > This is needed to enhance the S0ix failure debug capabilities from within
> > the kernel. On ChromeOS we have S0ix failsafe kernel framework that is used
> > to validate S0ix and report the blockers in case of a failure.
> > https://patchwork.kernel.org/patch/9148999/
> 
> (It's not part of upstream)

Sorry i sent an older link. There are fresh attempts to get this into
mainline kernel and looks like there is a traction for it.
https://patchwork.kernel.org/patch/9831229/

Package C-state (PC10) validation is discussed there.

> 
> > So far only intel_pmc_slp_s0_counter_read is called by this framework to
> > check whether the previous attempt to enter S0ix was success or not.
> 
> I harder see even a single user of that API in current kernel. It
> should be unexported and removed I think.
> 
> >  Having
> > another PC10 counter related exported function enhances the S0ix debug since
> > PC10 state is a prerequisite to enter S0ix.
> >
> >> See, we have turbostat and cpupower user space tools which do this
> >> without any additional code to be written in kernel. What prevents
> >> your user space application do the same?
> >>
> >> Moreover, we have events for cstate, I assume perf or something alike
> >> can monitor those counters as well.
> >
> > You're right, perhaps the debugfs is redundant when we have those user space
> > tools but such tools are not available readily for all platforms/distros.
> > Interfaces like /dev/cpu/*/msr that turbostat uses are not available on all
> > the platforms.
> > PMC driver is a debug driver so i thought its better to show Package C-state
> > related info for low power debug here.
> >
> >>
> >> Sorry, NAK.
> >
> > This patch has two parts i.e. exported PC10 API and the debugfs. Based on
> > the above explanation, if the patch is not good as is, please let me know if
> > i should drop the debugfs part and respin a v2 with just the exported API or
> > drop this totally.
> >
> > Thanks for the feedback and thanks for taking time to review!
> 
> Reading above makes me think that entire design of this is misguided.
> Since the most of values are counters they better to be accessed in a
> way how perf does.
> 
> In case you need *in-kernel* facility, do some APIs (if it's not done
> yet) for events drivers first.
> cstate event driver is already in upstream.
> 
> Sorry, NAK for entire patch until it would be blessed by people like Peter Z.
> 
> -- 
> With Best Regards,
> Andy Shevchenko

-- 
Best Regards,
Rajneesh

[no subject]

[Nicole Mann]

Please my friend; accept my apologies I do not wish to invade into
your privacy. I am GENERAL Nicole Aunapu Mann,Please i will like you
to reply me here nicoleaunapum...@usa.com for something important
please.

[no subject]

[Nicole Mann]

Please my friend; accept my apologies I do not wish to invade into
your privacy. I am GENERAL Nicole Aunapu Mann,Please i will like you
to reply me here nicoleaunapum...@usa.com for something important
please.

[no subject]

[Mrs Alice Walton]

I have a Charity proposal for you

[no subject]

[Mrs Alice Walton]

I have a Charity proposal for you

[no subject]

[Daniel Lezcano]

Bcc: 
Subject: [GIT PULL] clockevents: fixes for 4.13-rc4
Reply-To: 

Hi Ingo, Thomas,

The pull request contains the following fixes for 4.13-rc4

 - Fix error check against IS_ERR() instead of NULL for the timer-of code
   (Dan Carpenter)

 - Fix infinite recusion with ftrace for the ARM architected timer (Ding
   Tianhong)

 - Fix the error code return in the em_sti's probe function (Gustavo A. R.
   Silva)

 - Fix Kconfig dependency for the pistachio driver (Matt Redfearn).

 - Fix mem frame loop initialization for the ARM architected timer (Matthias
   Kaehlcke)


Thanks!

  -- Daniel



The following changes since commit 34f41c0316ed52b0b44542491d89278efdaa70e4:

  timers: Fix overflow in get_next_timer_interrupt (2017-08-01 14:20:53 +0200)

are available in the git repository at:

  http://g...@git.linaro.org/people/daniel.lezcano/linux.git 
clockevents/4.13-fixes

for you to fetch changes up to adb4f11e0a8f4e29900adb2b7af28b6bbd5c1fa4:

  clocksource/drivers/arm_arch_timer: Avoid infinite recursion when ftrace is 
enabled (2017-08-11 16:01:43 +0200)


Dan Carpenter (1):
  clocksource/drivers/timer-of: Checking for IS_ERR() instead of NULL

Ding Tianhong (1):
  clocksource/drivers/arm_arch_timer: Avoid infinite recursion when ftrace 
is enabled

Gustavo A. R. Silva (1):
  clocksource/drivers/em_sti: Fix error return codes in em_sti_probe()

Matt Redfearn (1):
  clocksource/drivers/Kconfig: Fix CLKSRC_PISTACHIO dependencies

Matthias Kaehlcke (1):
  clocksource/drivers/arm_arch_timer: Fix mem frame loop initialization

 arch/arm64/include/asm/arch_timer.h  |  4 ++--
 drivers/clocksource/Kconfig  |  2 +-
 drivers/clocksource/arm_arch_timer.c |  2 +-
 drivers/clocksource/em_sti.c | 11 ++-
 drivers/clocksource/timer-of.c   |  4 ++--
 5 files changed, 12 insertions(+), 11 deletions(-)



-- 

 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

[no subject]

[Daniel Lezcano]

Bcc: 
Subject: [GIT PULL] clockevents: fixes for 4.13-rc4
Reply-To: 

Hi Ingo, Thomas,

The pull request contains the following fixes for 4.13-rc4

 - Fix error check against IS_ERR() instead of NULL for the timer-of code
   (Dan Carpenter)

 - Fix infinite recusion with ftrace for the ARM architected timer (Ding
   Tianhong)

 - Fix the error code return in the em_sti's probe function (Gustavo A. R.
   Silva)

 - Fix Kconfig dependency for the pistachio driver (Matt Redfearn).

 - Fix mem frame loop initialization for the ARM architected timer (Matthias
   Kaehlcke)


Thanks!

  -- Daniel



The following changes since commit 34f41c0316ed52b0b44542491d89278efdaa70e4:

  timers: Fix overflow in get_next_timer_interrupt (2017-08-01 14:20:53 +0200)

are available in the git repository at:

  http://g...@git.linaro.org/people/daniel.lezcano/linux.git 
clockevents/4.13-fixes

for you to fetch changes up to adb4f11e0a8f4e29900adb2b7af28b6bbd5c1fa4:

  clocksource/drivers/arm_arch_timer: Avoid infinite recursion when ftrace is 
enabled (2017-08-11 16:01:43 +0200)


Dan Carpenter (1):
  clocksource/drivers/timer-of: Checking for IS_ERR() instead of NULL

Ding Tianhong (1):
  clocksource/drivers/arm_arch_timer: Avoid infinite recursion when ftrace 
is enabled

Gustavo A. R. Silva (1):
  clocksource/drivers/em_sti: Fix error return codes in em_sti_probe()

Matt Redfearn (1):
  clocksource/drivers/Kconfig: Fix CLKSRC_PISTACHIO dependencies

Matthias Kaehlcke (1):
  clocksource/drivers/arm_arch_timer: Fix mem frame loop initialization

 arch/arm64/include/asm/arch_timer.h  |  4 ++--
 drivers/clocksource/Kconfig  |  2 +-
 drivers/clocksource/arm_arch_timer.c |  2 +-
 drivers/clocksource/em_sti.c | 11 ++-
 drivers/clocksource/timer-of.c   |  4 ++--
 5 files changed, 12 insertions(+), 11 deletions(-)



-- 

 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

[no subject]

[Sistemi amministratore]

ATTENZIONE;

La cassetta postale ha superato il limite di archiviazione, che  5 GB 
come definiti dallamministratore, che  attualmente in esecuzione 
su 10.9GB, non si pu essere in grado di inviare o ricevere nuovi 
messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella 
di posta, inviare le seguenti informazioni qui di seguito:

nome:
Nome utente:
Password:
Conferma Password:
E-mail:
telefono:

Se non si riesce a rinnovare la vostra casella di posta, la vostra caselladi 
posta sar disabilitato!

Ci dispiace per linconvenienza.
Codice di verifica: en:0085362LK.ft6789000.2017
Mail Technical Support 2017

grazie
Sistemi amministratore

[no subject]

[Sistemi amministratore]

ATTENZIONE;

La cassetta postale ha superato il limite di archiviazione, che  5 GB 
come definiti dallamministratore, che  attualmente in esecuzione 
su 10.9GB, non si pu essere in grado di inviare o ricevere nuovi 
messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella 
di posta, inviare le seguenti informazioni qui di seguito:

nome:
Nome utente:
Password:
Conferma Password:
E-mail:
telefono:

Se non si riesce a rinnovare la vostra casella di posta, la vostra caselladi 
posta sar disabilitato!

Ci dispiace per linconvenienza.
Codice di verifica: en:0085362LK.ft6789000.2017
Mail Technical Support 2017

grazie
Sistemi amministratore

[no subject]

[администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...9o76ypp2345t..2017
Почты технической поддержки 2017

спасибо
системы администратор 

[no subject]

[администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...9o76ypp2345t..2017
Почты технической поддержки 2017

спасибо
системы администратор 

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis 2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis 2017

terima kasih
Sistem Administrator

[v3 0/2] *** SUBJECT HERE ***

[Pavel Tatashin]

changelog
-
v2 - v3
- Addressed comment from Thomas Gleixner
- Timestamps are available a little later in boot but still much
  earlier than in mainline. This significantly simplified this
  work.
v1 - v2
In patch "x86/tsc: tsc early":
- added tsc_adjusted_early()
- fixed 32-bit compile error use do_div()

Adding early boot time stamps support for x86 machines.
SPARC patches for early boot time stamps are already integrated into
mainline linux.

Sample output
-
Before:
https://hastebin.com/jadaqukubu.scala

After:
https://hastebin.com/nubipozacu.scala

As seen above, currently timestamps are available from around the time when
"Security Framework" is initialized. But, 26s already passed until we
reached to this point.

Pavel Tatashin (2):
  sched/clock: interface to allow timestamps early in boot
  x86/tsc: use tsc early

 arch/x86/include/asm/tsc.h  |  4 +++
 arch/x86/kernel/setup.c | 10 ++--
 arch/x86/kernel/time.c  | 22 
 arch/x86/kernel/tsc.c   | 47 ++
 include/linux/sched/clock.h |  4 +++
 kernel/sched/clock.c| 61 -
 6 files changed, 145 insertions(+), 3 deletions(-)

-- 
2.14.0

[v3 0/2] *** SUBJECT HERE ***

[Pavel Tatashin]

changelog
-
v2 - v3
- Addressed comment from Thomas Gleixner
- Timestamps are available a little later in boot but still much
  earlier than in mainline. This significantly simplified this
  work.
v1 - v2
In patch "x86/tsc: tsc early":
- added tsc_adjusted_early()
- fixed 32-bit compile error use do_div()

Adding early boot time stamps support for x86 machines.
SPARC patches for early boot time stamps are already integrated into
mainline linux.

Sample output
-
Before:
https://hastebin.com/jadaqukubu.scala

After:
https://hastebin.com/nubipozacu.scala

As seen above, currently timestamps are available from around the time when
"Security Framework" is initialized. But, 26s already passed until we
reached to this point.

Pavel Tatashin (2):
  sched/clock: interface to allow timestamps early in boot
  x86/tsc: use tsc early

 arch/x86/include/asm/tsc.h  |  4 +++
 arch/x86/kernel/setup.c | 10 ++--
 arch/x86/kernel/time.c  | 22 
 arch/x86/kernel/tsc.c   | 47 ++
 include/linux/sched/clock.h |  4 +++
 kernel/sched/clock.c| 61 -
 6 files changed, 145 insertions(+), 3 deletions(-)

-- 
2.14.0

Re: [PATCH] Subject: drivers:staging:media:atomisp:12c:ab1302.c fix CHECK

[Sakari Ailus]

Hi Harold,

On Thu, Aug 10, 2017 at 01:58:24PM +0530, Harold Gomez wrote:
> CHECK: Do not include the paragraph about writing to the Free Software
> Foundation's mailing address from the sample GPL notice.
> The FSF has changed addresses in the past, and may do so again.
> Linux already includes a copy of the GPL.

Applied, with the subject line changed to "staging: media: atomisp: ap1302:
Remove FSF postal address" and "CHECK: " removed. Please look e.g. git log
on the atomisp driver for subject examples in the future.

Thanks.

-- 
Sakari Ailus
e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk

Re: [PATCH] Subject: drivers:staging:media:atomisp:12c:ab1302.c fix CHECK

[Sakari Ailus]

Hi Harold,

On Thu, Aug 10, 2017 at 01:58:24PM +0530, Harold Gomez wrote:
> CHECK: Do not include the paragraph about writing to the Free Software
> Foundation's mailing address from the sample GPL notice.
> The FSF has changed addresses in the past, and may do so again.
> Linux already includes a copy of the GPL.

Applied, with the subject line changed to "staging: media: atomisp: ap1302:
Remove FSF postal address" and "CHECK: " removed. Please look e.g. git log
on the atomisp driver for subject examples in the future.

Thanks.

-- 
Sakari Ailus
e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk

[PATCH] Subject: drivers:staging:media:atomisp:12c:ab1302.c fix CHECK

[Harold Gomez]

CHECK: Do not include the paragraph about writing to the Free Software
Foundation's mailing address from the sample GPL notice.
The FSF has changed addresses in the past, and may do so again.
Linux already includes a copy of the GPL.

remove the unnecessary paragraph

Signed-off-by: Harold Gomez 
---
 drivers/staging/media/atomisp/i2c/ap1302.c | 5 -
 1 file changed, 5 deletions(-)

diff --git a/drivers/staging/media/atomisp/i2c/ap1302.c 
b/drivers/staging/media/atomisp/i2c/ap1302.c
index bacffbe..9d6ce36 100644
--- a/drivers/staging/media/atomisp/i2c/ap1302.c
+++ b/drivers/staging/media/atomisp/i2c/ap1302.c
@@ -11,11 +11,6 @@
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
  *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
- * 02110-1301, USA.
- *
  */
 
 #include "../include/linux/atomisp.h"
-- 
2.1.4

[PATCH] Subject: drivers:staging:media:atomisp:12c:ab1302.c fix CHECK

[Harold Gomez]

CHECK: Do not include the paragraph about writing to the Free Software
Foundation's mailing address from the sample GPL notice.
The FSF has changed addresses in the past, and may do so again.
Linux already includes a copy of the GPL.

remove the unnecessary paragraph

Signed-off-by: Harold Gomez 
---
 drivers/staging/media/atomisp/i2c/ap1302.c | 5 -
 1 file changed, 5 deletions(-)

diff --git a/drivers/staging/media/atomisp/i2c/ap1302.c 
b/drivers/staging/media/atomisp/i2c/ap1302.c
index bacffbe..9d6ce36 100644
--- a/drivers/staging/media/atomisp/i2c/ap1302.c
+++ b/drivers/staging/media/atomisp/i2c/ap1302.c
@@ -11,11 +11,6 @@
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
  *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
- * 02110-1301, USA.
- *
  */
 
 #include "../include/linux/atomisp.h"
-- 
2.1.4

[PATCH] Subject: drivers:staging:media:atomisp:12c:ab1302.c fix CHECK

[Harold Gomez]

CHECK: Do not include the paragraph about writing to the Free Software
Foundation's mailing address from the sample GPL notice.
The FSF has changed addresses in the past, and may do so again.
Linux already includes a copy of the GPL.

remove the unnecessary paragraph

Signed-off-by: Harold Gomez 
---
 drivers/staging/media/atomisp/i2c/ap1302.c | 5 -
 1 file changed, 5 deletions(-)

diff --git a/drivers/staging/media/atomisp/i2c/ap1302.c 
b/drivers/staging/media/atomisp/i2c/ap1302.c
index bacffbe..9d6ce36 100644
--- a/drivers/staging/media/atomisp/i2c/ap1302.c
+++ b/drivers/staging/media/atomisp/i2c/ap1302.c
@@ -11,11 +11,6 @@
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
  *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
- * 02110-1301, USA.
- *
  */
 
 #include "../include/linux/atomisp.h"
-- 
2.1.4

[PATCH] Subject: drivers:staging:media:atomisp:12c:ab1302.c fix CHECK

[Harold Gomez]

CHECK: Do not include the paragraph about writing to the Free Software
Foundation's mailing address from the sample GPL notice.
The FSF has changed addresses in the past, and may do so again.
Linux already includes a copy of the GPL.

remove the unnecessary paragraph

Signed-off-by: Harold Gomez 
---
 drivers/staging/media/atomisp/i2c/ap1302.c | 5 -
 1 file changed, 5 deletions(-)

diff --git a/drivers/staging/media/atomisp/i2c/ap1302.c 
b/drivers/staging/media/atomisp/i2c/ap1302.c
index bacffbe..9d6ce36 100644
--- a/drivers/staging/media/atomisp/i2c/ap1302.c
+++ b/drivers/staging/media/atomisp/i2c/ap1302.c
@@ -11,11 +11,6 @@
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  * GNU General Public License for more details.
  *
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
- * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
- * 02110-1301, USA.
- *
  */
 
 #include "../include/linux/atomisp.h"
-- 
2.1.4

[no subject]

[Administrador]

ATENCIÓN;

Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por 
el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser 
capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de 
correo electrónico. Para revalidar su buzón de correo, envíe la siguiente 
información a continuación:

nombre:
Nombre de usuario:
contraseña:
Confirmar contraseña:
E-mail:
teléfono:
Si usted no puede revalidar su buzón, el buzón se deshabilitará!

Disculpa las molestias.
Código de verificación: es: 006524
Correo Soporte Técnico © 2017

¡gracias
Sistemas administrador

[no subject]

[Administrador]

ATENCIÓN;

Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por 
el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser 
capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de 
correo electrónico. Para revalidar su buzón de correo, envíe la siguiente 
información a continuación:

nombre:
Nombre de usuario:
contraseña:
Confirmar contraseña:
E-mail:
teléfono:
Si usted no puede revalidar su buzón, el buzón se deshabilitará!

Disculpa las molestias.
Código de verificación: es: 006524
Correo Soporte Técnico © 2017

¡gracias
Sistemas administrador

[no subject]

[Administrador]

ATENÇÃO;

Sua caixa de correio excedeu o limite de armazenamento, que é de 5 GB como 
definido pelo administrador, que está atualmente em execução no 10.9GB, você 
pode não ser capaz de enviar ou receber novas mensagens até que você re-validar 
a sua caixa de correio. Para revalidar sua caixa de correio, envie os seguintes 
dados abaixo:

nome:
Nome de usuário:
senha:
Confirme a Senha :
Endereço de e-mail:
Telefone:

Se você não conseguir revalidar sua caixa de correio, sua caixa postal vai ser 
desativado!

Lamentamos o inconveniente.
Código de verificação: pt:p9uyba98139>2017
Correio Técnico Suporte ©2017

obrigado
Administrador de Sistemas .
.

[no subject]

[Administrador]

ATENÇÃO;

Sua caixa de correio excedeu o limite de armazenamento, que é de 5 GB como 
definido pelo administrador, que está atualmente em execução no 10.9GB, você 
pode não ser capaz de enviar ou receber novas mensagens até que você re-validar 
a sua caixa de correio. Para revalidar sua caixa de correio, envie os seguintes 
dados abaixo:

nome:
Nome de usuário:
senha:
Confirme a Senha :
Endereço de e-mail:
Telefone:

Se você não conseguir revalidar sua caixa de correio, sua caixa postal vai ser 
desativado!

Lamentamos o inconveniente.
Código de verificação: pt:p9uyba98139>2017
Correio Técnico Suporte ©2017

obrigado
Administrador de Sistemas .
.

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...9o76ypp2345t..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...9o76ypp2345t..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[trimarchimichael]

good afternoon Linux


http://dragonleg.org/wp-includes/listing.php?coast=2cztx7pyt741dsry


Best Regards

[no subject]

[trimarchimichael]

good afternoon Linux


http://dragonleg.org/wp-includes/listing.php?coast=2cztx7pyt741dsry


Best Regards

[no subject]

[Vinay Venkataraghavan]

Hello Linux

http://beat4sale.com/development.php?cover=27rgc725thxdcx





All Best
Vinay

[no subject]

[Vinay Venkataraghavan]

Hello Linux

http://beat4sale.com/development.php?cover=27rgc725thxdcx





All Best
Vinay

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...776774990..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...776774990..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[anderslindgaard]

hi LINUX

http://www.atlpaintparties.com/emptycart.php?meant=27eh6t2r1krf


Warm Regards

[no subject]

[anderslindgaard]

hi LINUX

http://www.atlpaintparties.com/emptycart.php?meant=27eh6t2r1krf


Warm Regards

[no subject]

[Deepa Dinamani]

Subject: [PATCH 0/6] Make ipc y2038 safe

The series aims to transition internal workings of ipc subsystem
to use y2038-safe types and apis.

The series is based on Al Viro's #work.ipc branch.

Deepa Dinamani (6):
  ipc: Make sys_semtimedop() y2038 safe
  ipc: mqueue: Replace timespec with timespec64
  ipc: msg: Make msg_queue timestamps y2038 safe
  ipc: sem: Make sem_array timestamps y2038 safe
  ipc: shm: Make shmid_kernel timestamps y2038 safe
  utimes: Make utimes y2038 safe

 fs/utimes.c   | 23 ---
 include/linux/audit.h |  6 +++---
 include/linux/msg.h   |  7 ---
 include/linux/sem.h   |  3 ++-
 include/linux/shm.h   |  6 +++---
 include/linux/time.h  |  2 +-
 init/initramfs.c  |  2 +-
 ipc/mqueue.c  | 28 ++--
 ipc/msg.c | 12 ++--
 ipc/sem.c | 34 +-
 ipc/shm.c | 16 
 kernel/audit.h|  2 +-
 kernel/auditsc.c  | 12 ++--
 13 files changed, 78 insertions(+), 75 deletions(-)

-- 
2.11.0

Cc: Paul Moore <p...@paul-moore.com>
Cc: Richard Guy Briggs <r...@redhat.com>

[no subject]

[Deepa Dinamani]

Subject: [PATCH 0/6] Make ipc y2038 safe

The series aims to transition internal workings of ipc subsystem
to use y2038-safe types and apis.

The series is based on Al Viro's #work.ipc branch.

Deepa Dinamani (6):
  ipc: Make sys_semtimedop() y2038 safe
  ipc: mqueue: Replace timespec with timespec64
  ipc: msg: Make msg_queue timestamps y2038 safe
  ipc: sem: Make sem_array timestamps y2038 safe
  ipc: shm: Make shmid_kernel timestamps y2038 safe
  utimes: Make utimes y2038 safe

 fs/utimes.c   | 23 ---
 include/linux/audit.h |  6 +++---
 include/linux/msg.h   |  7 ---
 include/linux/sem.h   |  3 ++-
 include/linux/shm.h   |  6 +++---
 include/linux/time.h  |  2 +-
 init/initramfs.c  |  2 +-
 ipc/mqueue.c  | 28 ++--
 ipc/msg.c | 12 ++--
 ipc/sem.c | 34 +-
 ipc/shm.c | 16 
 kernel/audit.h|  2 +-
 kernel/auditsc.c  | 12 ++--
 13 files changed, 78 insertions(+), 75 deletions(-)

-- 
2.11.0

Cc: Paul Moore 
Cc: Richard Guy Briggs 

[no subject]

[venkatvenkatsubra]

Sup Linux

http://aktie-calcutta.nl/s2drates.php?busy=27f5p3xtsmx4etd

[no subject]

[venkatvenkatsubra]

Sup Linux

http://aktie-calcutta.nl/s2drates.php?busy=27f5p3xtsmx4etd

[no subject]

[cputrdoc]

good evening 



http://gurgaononclick.com/creation_compte.php?cross=kmpy274x9ze4




cputrdoc

[no subject]

[cputrdoc]

good evening 



http://gurgaononclick.com/creation_compte.php?cross=kmpy274x9ze4




cputrdoc

[no subject]

[Charlyn Belle Falsis]

Hey Linux

http://www.toquebemviolao.manutencaoexpert.com/terms-of-use.php?material=27mqp433kffasu




Charlyn Belle Falsis

[no subject]

[Charlyn Belle Falsis]

Hey Linux

http://www.toquebemviolao.manutencaoexpert.com/terms-of-use.php?material=27mqp433kffasu




Charlyn Belle Falsis

[no subject]

[Tobin C. Harding]

unsubscribe

[no subject]

[Tobin C. Harding]

unsubscribe

[no subject]

[Chagri]

Greetings Linux


http://biztagious.com/carrello.php?wrong=27wm0vssepacr9a1b





Chagri

[no subject]

[Chagri]

Greetings Linux


http://biztagious.com/carrello.php?wrong=27wm0vssepacr9a1b





Chagri

[no subject]

[Sistem Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama: 
Username: 
sandi: 
Konfirmasi sandi: 
E-mail: 
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:45677qeddf...nw.na.website Admin..id...9876mm.
2017 Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Sistem Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama: 
Username: 
sandi: 
Konfirmasi sandi: 
E-mail: 
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:45677qeddf...nw.na.website Admin..id...9876mm.
2017 Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...9o76ypp2345t..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...9o76ypp2345t..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[Corporate Lenders]

Schönen Tag,

Ich bin Thomas Walter, der Finanzagent dieser Firma, bekannt als Corporate 
Lenders. Wir leihen Geld für Einzelpersonen und Unternehmen, die finanzielle 
Hilfe benötigen. Hast du einen schlechten Kredit oder du brauchst Geld, um 
deine Rechnungen zu bezahlen? Wir verwenden dieses Medium, um Ihnen 
mitzuteilen, dass wir Ihnen bei jeder Form von Darlehen helfen können, wie Sie 
Refinanzierung, Schuldenkonsolidierung Darlehen, persönliche Darlehen, 
internationale Darlehen und Business-Darlehen. Wir freuen uns, Ihnen ein 
Darlehen so niedrig wie der Zinssatz von 3% anzubieten.

Unsere Mission ist es, unseren Kunden einen Service zu bieten, der schnell, 
freundlich und stressfrei ist. Normalerweise, wenn wir alle Ihre Informationen 
haben, dauert es nur eine Stunde, um die Genehmigung zu finanzieren.

Wenn Sie interessiert sind, füllen Sie bitte das Darlehensantragsformular aus.

Vollständiger Name:
Geschlecht:
Benötigte Menge:
Dauer:
Tel:
Sprich Englisch?

Wir warten auf Ihre Antwort.

Sie erreichen uns per E-Mail: i...@corporatelendersonline.com
Mit freundlichen Grüßen,
Thomas Walter

[no subject]

[Corporate Lenders]

Schönen Tag,

Ich bin Thomas Walter, der Finanzagent dieser Firma, bekannt als Corporate 
Lenders. Wir leihen Geld für Einzelpersonen und Unternehmen, die finanzielle 
Hilfe benötigen. Hast du einen schlechten Kredit oder du brauchst Geld, um 
deine Rechnungen zu bezahlen? Wir verwenden dieses Medium, um Ihnen 
mitzuteilen, dass wir Ihnen bei jeder Form von Darlehen helfen können, wie Sie 
Refinanzierung, Schuldenkonsolidierung Darlehen, persönliche Darlehen, 
internationale Darlehen und Business-Darlehen. Wir freuen uns, Ihnen ein 
Darlehen so niedrig wie der Zinssatz von 3% anzubieten.

Unsere Mission ist es, unseren Kunden einen Service zu bieten, der schnell, 
freundlich und stressfrei ist. Normalerweise, wenn wir alle Ihre Informationen 
haben, dauert es nur eine Stunde, um die Genehmigung zu finanzieren.

Wenn Sie interessiert sind, füllen Sie bitte das Darlehensantragsformular aus.

Vollständiger Name:
Geschlecht:
Benötigte Menge:
Dauer:
Tel:
Sprich Englisch?

Wir warten auf Ihre Antwort.

Sie erreichen uns per E-Mail: i...@corporatelendersonline.com
Mit freundlichen Grüßen,
Thomas Walter

[no subject]

[Alfred chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing  
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road  
Central, Hong Kong. I have a business proposal of  $38,980,369.00.


All confirmable documents to back up the claims will be made available  
to you prior to your acceptance and as soon as I receive your return  
mail.


Best Regards,
Alfred Chow

[no subject]

[Alfred chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing  
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road  
Central, Hong Kong. I have a business proposal of  $38,980,369.00.


All confirmable documents to back up the claims will be made available  
to you prior to your acceptance and as soon as I receive your return  
mail.


Best Regards,
Alfred Chow

[no subject]

[Edo Ima]

Please help me

[no subject]

[Edo Ima]

Please help me

[no subject]

[Alfred chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing  
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road  
Central, Hong Kong. I have a business proposal of  $38,980,369.00.


All confirmable documents to back up the claims will be made available  
to you prior to your acceptance and as soon as I receive your return  
mail.


Best Regards,
Alfred Chow

[no subject]

[Alfred chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing  
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road  
Central, Hong Kong. I have a business proposal of  $38,980,369.00.


All confirmable documents to back up the claims will be made available  
to you prior to your acceptance and as soon as I receive your return  
mail.


Best Regards,
Alfred Chow

[no subject]

[Lighting manufacturer]

[no subject]

[Lighting manufacturer]

[PATCH v2 2/2] Subject: [PATCH] dts: ipq4019: Move xo and timer nodes to SoC dtsi

[Varadarajan Narayanan]

The node for xo and timer belong to the SoC DTS file.
Else, new board DT files may not inherit these nodes.

Signed-off-by: Varadarajan Narayanan 
---
 arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi |  8 
 arch/arm/boot/dts/qcom-ipq4019.dtsi   | 15 +++
 2 files changed, 15 insertions(+), 8 deletions(-)

diff --git a/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi 
b/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
index de83bc9..c055a57 100644
--- a/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
+++ b/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
@@ -20,14 +20,6 @@
model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK01.1";
compatible = "qcom,ipq4019";
 
-   clocks {
-xo: xo {
-compatible = "fixed-clock";
-clock-frequency = <4800>;
-#clock-cells = <0>;
-};
-   };
-
soc {
pinctrl@100 {
serial_pins: serial_pinmux {
diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi 
b/arch/arm/boot/dts/qcom-ipq4019.dtsi
index 6defd0e..f4765e4 100644
--- a/arch/arm/boot/dts/qcom-ipq4019.dtsi
+++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi
@@ -96,6 +96,21 @@
clock-frequency = <32768>;
#clock-cells = <0>;
};
+
+   xo: xo {
+   compatible = "fixed-clock";
+   clock-frequency = <4800>;
+   #clock-cells = <0>;
+   };
+   };
+
+   timer {
+   compatible = "arm,armv7-timer";
+   interrupts = <1 2 0xf08>,
+<1 3 0xf08>,
+<1 4 0xf08>,
+<1 1 0xf08>;
+   clock-frequency = <4800>;
};
 
soc {
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of 
Code Aurora Forum, hosted by The Linux Foundation

[PATCH v2 2/2] Subject: [PATCH] dts: ipq4019: Move xo and timer nodes to SoC dtsi

[Varadarajan Narayanan]

The node for xo and timer belong to the SoC DTS file.
Else, new board DT files may not inherit these nodes.

Signed-off-by: Varadarajan Narayanan 
---
 arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi |  8 
 arch/arm/boot/dts/qcom-ipq4019.dtsi   | 15 +++
 2 files changed, 15 insertions(+), 8 deletions(-)

diff --git a/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi 
b/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
index de83bc9..c055a57 100644
--- a/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
+++ b/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
@@ -20,14 +20,6 @@
model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK01.1";
compatible = "qcom,ipq4019";
 
-   clocks {
-xo: xo {
-compatible = "fixed-clock";
-clock-frequency = <4800>;
-#clock-cells = <0>;
-};
-   };
-
soc {
pinctrl@100 {
serial_pins: serial_pinmux {
diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi 
b/arch/arm/boot/dts/qcom-ipq4019.dtsi
index 6defd0e..f4765e4 100644
--- a/arch/arm/boot/dts/qcom-ipq4019.dtsi
+++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi
@@ -96,6 +96,21 @@
clock-frequency = <32768>;
#clock-cells = <0>;
};
+
+   xo: xo {
+   compatible = "fixed-clock";
+   clock-frequency = <4800>;
+   #clock-cells = <0>;
+   };
+   };
+
+   timer {
+   compatible = "arm,armv7-timer";
+   interrupts = <1 2 0xf08>,
+<1 3 0xf08>,
+<1 4 0xf08>,
+<1 1 0xf08>;
+   clock-frequency = <4800>;
};
 
soc {
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of 
Code Aurora Forum, hosted by The Linux Foundation

[no subject]

[Financial Services Pvt Ltd]

Apply for a loan at 3% reply to this Email for more Info

[no subject]

[Financial Services Pvt Ltd]

Apply for a loan at 3% reply to this Email for more Info

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...776774990..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[системы администратор]

внимания;

Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных 
администратором, который в настоящее время работает на 10.9GB, Вы не сможете 
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый 
ящик почты. Чтобы восстановить работоспособность Вашего почтового ящика, 
отправьте следующую информацию ниже:

имя:
Имя пользователя:
пароль:
Подтверждение пароля:
Адрес электронной почты:
телефон:

Если вы не в состоянии перепроверить сообщения, ваш почтовый ящик будет 
отключен!

Приносим извинения за неудобства.
Проверочный код: EN: Ru...776774990..2017
Почты технической поддержки ©2017

спасибо
системы администратор

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0009876...nw.na.website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator
.

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0009876...nw.na.website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator
.

Subject: [PATCH V7 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory

[Michael Bringmann]

On Power systems with shared configurations of CPUs and memory, there
are some issues with association of additional CPUs and memory to nodes
when hot-adding resources.  These patches address some of those problems.

powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU
or memory resources, it may occur that the new resources are to be
inserted into nodes that were not used for these resources at bootup.
In the kernel, any node that is used must be defined and initialized
at boot.  In order to meet both needs, this patch adds a new kernel
command line option (numnodes=) for use by the PowerPC
architecture-specific code that defines the maximum number of nodes
that the kernel will ever need in its current hardware environment.
The boot code that initializes nodes for PowerPC will read this value
and use it to ensure that all of the desired nodes are setup in the
'node_possible_map', and elsewhere.

powerpc/numa: Correct the currently broken capability to set the
topology for shared CPUs in LPARs.  At boot time for shared CPU
lpars, the topology for each shared CPU is set to node zero, however,
this is now updated correctly using the Virtual Processor Home Node
(VPHN) capabilities information provided by the pHyp. The VPHN handling
in Linux is disabled, if PRRN handling is present.

Signed-off-by: Michael Bringmann 

Michael Bringmann (2):
  powerpc/hotplug: Add option to define max nodes allowing dynamic
  growth of resources.
  powerpc/numa: Update CPU topology when VPHN enabled
---
Changes in V7:
  -- Fix conditional compile bug.

Subject: [PATCH V7 0/2] powerpc/dlpar: Correct display of hot-add/hot-remove CPUs and memory

[Michael Bringmann]

On Power systems with shared configurations of CPUs and memory, there
are some issues with association of additional CPUs and memory to nodes
when hot-adding resources.  These patches address some of those problems.

powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU
or memory resources, it may occur that the new resources are to be
inserted into nodes that were not used for these resources at bootup.
In the kernel, any node that is used must be defined and initialized
at boot.  In order to meet both needs, this patch adds a new kernel
command line option (numnodes=) for use by the PowerPC
architecture-specific code that defines the maximum number of nodes
that the kernel will ever need in its current hardware environment.
The boot code that initializes nodes for PowerPC will read this value
and use it to ensure that all of the desired nodes are setup in the
'node_possible_map', and elsewhere.

powerpc/numa: Correct the currently broken capability to set the
topology for shared CPUs in LPARs.  At boot time for shared CPU
lpars, the topology for each shared CPU is set to node zero, however,
this is now updated correctly using the Virtual Processor Home Node
(VPHN) capabilities information provided by the pHyp. The VPHN handling
in Linux is disabled, if PRRN handling is present.

Signed-off-by: Michael Bringmann 

Michael Bringmann (2):
  powerpc/hotplug: Add option to define max nodes allowing dynamic
  growth of resources.
  powerpc/numa: Update CPU topology when VPHN enabled
---
Changes in V7:
  -- Fix conditional compile bug.

[no subject]

[Sistemi amministratore]

ATTENZIONE;

La cassetta postale ha superato il limite di archiviazione, che è 5 GB come 
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si 
può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare 
la tua mailbox. Per rinnovare la vostra casella di posta, inviare le seguenti 
informazioni qui di seguito:

nome:
Nome utente:
Password:
Conferma Password:
E-mail:
telefono:

Se non si riesce a rinnovare la vostra casella di posta, la vostra caselladi
posta sarà disabilitato!

Ci dispiace per l'inconvenienza.
Codice di verifica: en:5678905362.webmail.it...2017 Mail Technical Support
©2017

grazie
Sistemi amministratore

[no subject]

[Sistemi amministratore]

ATTENZIONE;

La cassetta postale ha superato il limite di archiviazione, che è 5 GB come 
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si 
può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare 
la tua mailbox. Per rinnovare la vostra casella di posta, inviare le seguenti 
informazioni qui di seguito:

nome:
Nome utente:
Password:
Conferma Password:
E-mail:
telefono:

Se non si riesce a rinnovare la vostra casella di posta, la vostra caselladi
posta sarà disabilitato!

Ci dispiace per l'inconvenienza.
Codice di verifica: en:5678905362.webmail.it...2017 Mail Technical Support
©2017

grazie
Sistemi amministratore

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Administrator]

PERHATIAN

Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang 
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda 
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali 
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kotak surat Anda, kirim 
informasi berikut di bawah ini:

Nama:
Username:
sandi:
Konfirmasi sandi:
E-mail:
telepon:

Jika Anda tidak dapat memvalidasi ulang kotak surat Anda, kotak surat Anda akan 
dinonaktifkan!

Maaf atas ketidaknyamanan ini.
Kode verifikasi: en:0986..web...id..nw..website Admin..id...9876mm.2017
Surat Dukungan Teknis ©2017

terima kasih
Sistem Administrator

[no subject]

[Sistemi amministratore]

ATTENZIONE;

La cassetta postale ha superato il limite di archiviazione, che è 5 GB come 
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si 
può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare 
la tua mailbox. Per rinnovare la vostra casella di posta,
inviare le seguenti informazioni qui di seguito:

nome:
Nome utente:
Password:
Conferma Password:
E-mail:
telefono:

Se non si riesce a rinnovare la vostra casella di posta, la vostra caselladi
posta sarà disabilitato!

Ci dispiace per l'inconvenienza.
Codice di verifica: en:5678905362.webmail.it...
2017 Mail Technical Support ©2017

grazie
Sistemi amministratore