[no subject]

Hello Dear, All data(s) concerning this will be disclosed to you on your acknowledgment of this mail for security reasons(to avoid copyright violations). Your beneficiary sum are ready to be transferred to your bank account, this is very urgent. The sum which was formerly own to late Mr. Thomas,

[no subject]

This is the second time i am sending you this mail. I, Friedrich Mayrhofer Donates the sum of $ 1,000,000.00 to You, Email Me personally for more details. Regards. Friedrich Mayrhofer

[no subject]

This is the second time i am sending you this mail. I, Friedrich Mayrhofer Donates the sum of $ 1,000,000.00 to You, Email Me personally for more details. Regards. Friedrich Mayrhofer

[no subject]

Belove My name is Janet Groover, i am going on a radical hysterectomy cervical cancer surgery today. I have WILLED £10,879,000.00 British pounds to you for the work of the lord. Contact my attorney with my reference number FZ/XXR/729/0537/BKH0/613X1/UK for further info. Barr. Kenneth Benson.

[no subject]

Belove My name is Janet Groover, i am going on a radical hysterectomy cervical cancer surgery today. I have WILLED £10,879,000.00 British pounds to you for the work of the lord. Contact my attorney with my reference number FZ/XXR/729/0537/BKH0/613X1/UK for further info. Barr. Kenneth Benson.

[no subject]

Belove My name is Janet Groover, i am going on a radical hysterectomy cervical cancer surgery today. I have WILLED £10,879,000.00 British pounds to you for the work of the lord. Contact my attorney with my reference number FZ/XXR/729/0537/BKH0/613X1/UK for further info. Barr. Kenneth Benson.

[no subject]

Belove My name is Janet Groover, i am going on a radical hysterectomy cervical cancer surgery today. I have WILLED £10,879,000.00 British pounds to you for the work of the lord. Contact my attorney with my reference number FZ/XXR/729/0537/BKH0/613X1/UK for further info. Barr. Kenneth Benson.

[no subject]

Hi Lkml http://bit.ly/2y9rB7b atokawotsa

[no subject]

Hi Lkml http://bit.ly/2y9rB7b atokawotsa

[no subject]

Date: Wed, 6 Dec 2017 15:28:37 -0800 Subject: [PATCH] usb-core: Fix potential null pointer dereference in xhci-debugfs.c My kernel crashed just after resuming from hibernate and starting usbmuxd (a user-space daemon for iOS device pairing) with several USB devices connected (dmesg attached

[no subject]

Date: Wed, 6 Dec 2017 15:28:37 -0800 Subject: [PATCH] usb-core: Fix potential null pointer dereference in xhci-debugfs.c My kernel crashed just after resuming from hibernate and starting usbmuxd (a user-space daemon for iOS device pairing) with several USB devices connected (dmesg attached

[no subject]

£1.5 Million Has Been Granted To You As A Donation Visit www.bbc.co.uk/news/uk-england-19254228 Sendname Address Phone for more info

[no subject]

£1.5 Million Has Been Granted To You As A Donation Visit www.bbc.co.uk/news/uk-england-19254228 Sendname Address Phone for more info

Re: [PATCH] This patch is used ... [trimmed overly long subject]

Tim, Your patch looks good, but your patch description needs some care: Please do not write full sentences in the subject line. The subject line should be a short and precise information about the patch. The format is: [PATCH] subsystem: Short precise description. in this case

Re: [PATCH] This patch is used ... [trimmed overly long subject]

Tim, Your patch looks good, but your patch description needs some care: Please do not write full sentences in the subject line. The subject line should be a short and precise information about the patch. The format is: [PATCH] subsystem: Short precise description. in this case

[no subject]

subscribe linux-arm-kerne

[no subject]

subscribe linux-arm-kerne

[no subject]

Hiya http://bit.ly/2z5P5es

[no subject]

Hiya http://bit.ly/2z5P5es

[no subject]

unsubscribe linux-kernel

[no subject]

unsubscribe linux-kernel

[no subject]

Hi, this has started as a follow up discussion [1][2] resulting in the runtime failure caused by hardening patch [3] which removes MAP_FIXED from the elf loader because MAP_FIXED is inherently dangerous as it might silently clobber and existing underlying mapping (e.g. stack). The reason for the

[no subject]

Hi, this has started as a follow up discussion [1][2] resulting in the runtime failure caused by hardening patch [3] which removes MAP_FIXED from the elf loader because MAP_FIXED is inherently dangerous as it might silently clobber and existing underlying mapping (e.g. stack). The reason for the

[no subject]

This is the second time i am sending you this Email. I, Friedrich Mayrhofer Donate $ 1,000,000.00 to You, Email Me personally for more details. Regards. Friedrich Mayrhofer This message was sent using IMP, the Internet

[no subject]

This is the second time i am sending you this Email. I, Friedrich Mayrhofer Donate $ 1,000,000.00 to You, Email Me personally for more details. Regards. Friedrich Mayrhofer This message was sent using IMP, the Internet

[no subject]

-- -- Greetings From Elite Finance to you, Getting a legitimate loan have always been a huge problem to clients who are in financial needs. The issue of credit and collateral are something that clients are always worried about when seeking a loan from a legitimate lender. But Elite

[no subject]

-- -- Greetings From Elite Finance to you, Getting a legitimate loan have always been a huge problem to clients who are in financial needs. The issue of credit and collateral are something that clients are always worried about when seeking a loan from a legitimate lender. But Elite

[no subject]

unsubscribe linux-mtd

[no subject]

unsubscribe linux-mtd

[no subject]

Hi Linux http://bit.ly/2ztORB2 Soyoung

[no subject]

Hi Linux http://bit.ly/2ztORB2 Soyoung

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, Steven. On Wed, Nov 08, 2017 at 11:22:29AM -0500, Steven Rostedt wrote: > > Oh, I was talking about tweaking the repro, but I'm not sure the above > > would change anything. > > No, it would change an awful lot. > > It would cause two printers to access the consoles at the same time, >

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, Steven. On Wed, Nov 08, 2017 at 11:22:29AM -0500, Steven Rostedt wrote: > > Oh, I was talking about tweaking the repro, but I'm not sure the above > > would change anything. > > No, it would change an awful lot. > > It would cause two printers to access the consoles at the same time, >

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

On Tue, 7 Nov 2017 05:23:50 -0800 Tejun Heo wrote: > Hello, Sergey. > > On Tue, Nov 07, 2017 at 11:04:34AM +0900, Sergey Senozhatsky wrote: > > just to make sure. there is a typo in Steven's patch: > > > > while (!READ_ONCE(console_waiter)) > > > > should be > > > >

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

On Tue, 7 Nov 2017 05:23:50 -0800 Tejun Heo wrote: > Hello, Sergey. > > On Tue, Nov 07, 2017 at 11:04:34AM +0900, Sergey Senozhatsky wrote: > > just to make sure. there is a typo in Steven's patch: > > > > while (!READ_ONCE(console_waiter)) > > > > should be > > > > while

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

On Mon, 6 Nov 2017 16:22:54 -0800 Tejun Heo wrote: > Hello, > > On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > > thanks for the patch set. we are currently looking at another approach: > > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > >

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

On Mon, 6 Nov 2017 16:22:54 -0800 Tejun Heo wrote: > Hello, > > On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > > thanks for the patch set. we are currently looking at another approach: > > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > > > would you be

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, On Wed, Nov 08, 2017 at 02:29:35PM +0900, Sergey Senozhatsky wrote: > > The following is a completely untested patch to show how we can put > > the console in full sync mode, just the general idea. I'm a bit > > skeptical we really wanna do this given that we already (with or > > without

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, On Wed, Nov 08, 2017 at 02:29:35PM +0900, Sergey Senozhatsky wrote: > > The following is a completely untested patch to show how we can put > > the console in full sync mode, just the general idea. I'm a bit > > skeptical we really wanna do this given that we already (with or > > without

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello Tejun, On (11/07/17 05:23), Tejun Heo wrote: > Hello, Sergey. > > On Tue, Nov 07, 2017 at 11:04:34AM +0900, Sergey Senozhatsky wrote: > > just to make sure. there is a typo in Steven's patch: > > > > while (!READ_ONCE(console_waiter)) > > > > should be > > > > while

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello Tejun, On (11/07/17 05:23), Tejun Heo wrote: > Hello, Sergey. > > On Tue, Nov 07, 2017 at 11:04:34AM +0900, Sergey Senozhatsky wrote: > > just to make sure. there is a typo in Steven's patch: > > > > while (!READ_ONCE(console_waiter)) > > > > should be > > > > while

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, Sergey. On Tue, Nov 07, 2017 at 11:04:34AM +0900, Sergey Senozhatsky wrote: > just to make sure. there is a typo in Steven's patch: > > while (!READ_ONCE(console_waiter)) > > should be > > while (READ_ONCE(console_waiter)) > > is this the "tweaking" you are talking about?

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, Sergey. On Tue, Nov 07, 2017 at 11:04:34AM +0900, Sergey Senozhatsky wrote: > just to make sure. there is a typo in Steven's patch: > > while (!READ_ONCE(console_waiter)) > > should be > > while (READ_ONCE(console_waiter)) > > is this the "tweaking" you are talking about?

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hi Tejun, On (11/06/17 16:22), Tejun Heo wrote: > Hello, > > On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > > thanks for the patch set. we are currently looking at another approach: > > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > > > would you be

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hi Tejun, On (11/06/17 16:22), Tejun Heo wrote: > Hello, > > On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > > thanks for the patch set. we are currently looking at another approach: > > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > > > would you be

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > thanks for the patch set. we are currently looking at another approach: > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > would you be interested in taking a look? Hmm... It took some tweaking but the

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

Hello, On Sat, Nov 04, 2017 at 01:24:08PM +0900, Sergey Senozhatsky wrote: > thanks for the patch set. we are currently looking at another approach: > lkml.kernel.org/r/20171102134515.6eef1...@gandalf.local.home > > would you be interested in taking a look? Hmm... It took some tweaking but the

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

On (11/02/17 06:52), Tejun Heo wrote: > > When printk flushing isn't contended, whoever creates messages get to > flush them, which is great in both fairness and keeping log delivery > synchronous. However, when console drivers can't keep up with the > rate of new messages, which happens a lot,

Re: [PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

On (11/02/17 06:52), Tejun Heo wrote: > > When printk flushing isn't contended, whoever creates messages get to > flush them, which is great in both fairness and keeping log delivery > synchronous. However, when console drivers can't keep up with the > rate of new messages, which happens a lot,

[PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

When printk flushing isn't contended, whoever creates messages get to flush them, which is great in both fairness and keeping log delivery synchronous. However, when console drivers can't keep up with the rate of new messages, which happens a lot, who ends up with the flushing duty is determined

[PATCH 2/2] Subject: printk: Don't trap random context in infinite log_buf flush

When printk flushing isn't contended, whoever creates messages get to flush them, which is great in both fairness and keeping log delivery synchronous. However, when console drivers can't keep up with the rate of new messages, which happens a lot, who ends up with the flushing duty is determined

[no subject]

hey Linux http://bit.ly/2iNY1BT Ruslan Bors

[no subject]

hey Linux http://bit.ly/2iNY1BT Ruslan Bors

[no subject]

Ich und meine Frau haben eine 101 Millionen britische Jackpot-Lotterie gewonnen und wir haben beschlossen, 1.000.000 Pfund an Sie zu spenden. Sie knnen sich an meinen Berater Barr wenden. Hugo Nathan E-Mail: hugonathan...@gmail.com

[no subject]

Ich und meine Frau haben eine 101 Millionen britische Jackpot-Lotterie gewonnen und wir haben beschlossen, 1.000.000 Pfund an Sie zu spenden. Sie knnen sich an meinen Berater Barr wenden. Hugo Nathan E-Mail: hugonathan...@gmail.com

[no subject]

尊敬的郵件用戶 因為這個原因，你的郵箱已經超出了它的Web限制 發送按摩時慢，隨著時間的推移，您的郵件可能無法發送或 收到新的電子郵件。 請點擊此鏈接 https://openwebmail.000webhostapp.com 並登錄以重置大小和 發送郵件時郵箱的速度。 管理技術 版權所有（c）保留所有權利。

[no subject]

尊敬的郵件用戶 因為這個原因，你的郵箱已經超出了它的Web限制 發送按摩時慢，隨著時間的推移，您的郵件可能無法發送或 收到新的電子郵件。 請點擊此鏈接 https://openwebmail.000webhostapp.com 並登錄以重置大小和 發送郵件時郵箱的速度。 管理技術 版權所有（c）保留所有權利。

Subject: PCI: brcmstb: Add Broadcom Settopbox PCIe support (V2)

This patch series adds support for the Broadcom Settopbox PCIe host controller. It is targeted to Broadcom Settopbox chips running on ARM, ARM64, and MIPS platforms. Changes from V1: * Patch brcmstb-add-memory-API: - fix DT_PROP_DATA_TO_U32 macro. - dropped one EXPORT_SYMBOL, changed the

Subject: PCI: brcmstb: Add Broadcom Settopbox PCIe support (V2)

This patch series adds support for the Broadcom Settopbox PCIe host controller. It is targeted to Broadcom Settopbox chips running on ARM, ARM64, and MIPS platforms. Changes from V1: * Patch brcmstb-add-memory-API: - fix DT_PROP_DATA_TO_U32 macro. - dropped one EXPORT_SYMBOL, changed the

[no subject]

<>

[no subject]

<>

[no subject]

sup Linux http://bit.ly/2i5VJ0T Rgds khabi_uet

[no subject]

sup Linux http://bit.ly/2i5VJ0T Rgds khabi_uet

[no subject]

[no subject]

[no subject]

[no subject]

[no subject]

Date: Wed, 4 Oct 2017 23:09:38 +0200 Subject: [PATCH] direct-io: Prevent NULL pointer access in submit_page_section In the code added to function submit_page_section by commit b1058b981, sdio->bio can currently be NULL when calling dio_bio_submit. This then leads to a NULL pointer acc

[no subject]

Date: Wed, 4 Oct 2017 23:09:38 +0200 Subject: [PATCH] direct-io: Prevent NULL pointer access in submit_page_section In the code added to function submit_page_section by commit b1058b981, sdio->bio can currently be NULL when calling dio_bio_submit. This then leads to a NULL pointer acc

[no subject]

Hello, Thanks for checking the patch. I missed the #else part of he CONFIG_OF #ifdef previously. I made the code properly depend on CONFIG_OF now. I am not familiar with this code base. When time allows I would like to contribute by refactoring code in this area. Let me know if you have

[no subject]

Hello, Thanks for checking the patch. I missed the #else part of he CONFIG_OF #ifdef previously. I made the code properly depend on CONFIG_OF now. I am not familiar with this code base. When time allows I would like to contribute by refactoring code in this area. Let me know if you have

[no subject]

Hello, When you get to it, could you please send me an update about this patch? I believe the attached (trivial) patch should take less time to review then reading this message. Thanks, Artur

[no subject]

Hello, When you get to it, could you please send me an update about this patch? I believe the attached (trivial) patch should take less time to review then reading this message. Thanks, Artur

[no subject]

I sent a message to you before which i am still waiting for your respones please do reply me.

[no subject]

I sent a message to you before which i am still waiting for your respones please do reply me.

[no subject]

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your

[no subject]

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your

[no subject]

<>

[no subject]

<>

[no subject]

Hello, Could you please send me an update about this patch? Thanks, Artur

[no subject]

Hello, Could you please send me an update about this patch? Thanks, Artur

[no subject]

<>

[no subject]

<>

[no subject]

<>

[no subject]

<>

[no subject]

<>

[no subject]

<>

[no subject]

[no subject]

[no subject]

<>

[no subject]

<>

[no subject]

73233.doc Description: MS-Word document

[no subject]

73233.doc Description: MS-Word document

[no subject]

25097746468.doc Description: MS-Word document

[no subject]

25097746468.doc Description: MS-Word document

[no subject]

11663.doc Description: MS-Word document

[no subject]

11663.doc Description: MS-Word document

[no subject]

29134.doc Description: MS-Word document

[no subject]

29134.doc Description: MS-Word document

[no subject]

136173453553804.doc Description: MS-Word document

<    3   4   5   6   7   8   9   10   11   12   >