Re: Question about Reiser4

On Mon, 2007-04-23 at 20:19 -0400, Theodore Tso wrote: > Sure, but Hans wants to change /etc/inetd.conf into /etc/inetd.conf.d, > where you have: /etc/inetd.conf.d/telnet/port, > /etc/inetd.conf.d/telnet/protocol, /etc/inetd.conf.d/telnet/wait, > /etc/inetd.conf.d/telnet/userid, /etc/inetd.conf.d/t

Re: 2.6.21-rc7: HPET enabled freeze my machine at boot

John, Just a doubt, you want me to test the patch with dynticks disabled? Guilherme M. Schroeder Network Administrator Central de Vendas Informatica LTDA Tel.: (11) 3665-2000 Ramal: 2008 http://www.centralinf.com.br john stultz wrote: On Mon, 2007-04-23 at 15:30 -0700, john stultz wrote: On

Re: 2.6.21-rc7: HPET enabled freeze my machine at boot

John, The dynticks doesn't affect HPET here at all. The machine freeze with or w/o dynticks. Gonna try the patch and i tell you. Guilherme M. Schroeder Network Administrator Central de Vendas Informatica LTDA Tel.: (11) 3665-2000 Ramal: 2008 http://www.centralinf.com.br john stultz

Re: 2.6.21-rc7: HPET enabled freeze my machine at boot

John, Removing the three lines doesn't help too. It just boot ok with clocksource=acpi_pm. Guilherme M. Schroeder Network Administrator Central de Vendas Informatica LTDA Tel.: (11) 3665-2000 Ramal: 2008 http://www.centralinf.com.br john stultz wrote: On Mon, 2007-04-23 at 15:30

INIT IPI help

Hello, I have Linux kernel 2.6.20-rc5 running on an AMD64 CPU, although I'm running an i386 (not amd64) kernel. I need to send an INIT inter-processor-interrupt from the BSP to all APs (there is one AP in my case since my system has a dual-core CPU). After using CPU-hotplug to disable CPU1, I am

Re: [PATCH] remove availability for PAGE_SIZE and friends (i386)

On Tue, 2007-03-06 at 08:31 -0800, David Brown wrote: > +#define __KERNEL__ That's a #define, not an #ifdef... - DML - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-in

Re: [patch 2/5] signalfd v2 - signalfd core ...

On Wed, 2007-03-07 at 17:21 -0800, Davide Libenzi wrote: > int signalfd_dequeue(int fd, siginfo_t *info, long timeo); > > The "fd" parameter must ba a signalfd file descriptor. The "info" parameter > is a pointer to the siginfo that will receive the dequeued signal, and > "timeo" is a timeout in m

Re: [GIT PULL] Documentation: Add a file explaining the requested Linux kernel license enforcement policy

gpl-guidepa2.html#x17-116000II https://copyleft.org/guide/comprehensive-gpl-guidepa3.html#x26-152000III I think the latter (the case studies) are particularly useful and my talk on the most recent case study was well-received at Embedded Linux Conference 2015. -- Bradley M. Kuhn Distinguished Technolo

RE: [PATCH v3] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410

Original Message Subject: Re: [PATCH v3] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410 From: Pali Rohár Date: Sat, November 11, 2017 4:12 pm To: Darren Hart Cc: Matthew Garrett , Andy Shevchenko , "Gabriel M. Elder" , Gabriel

Hello Dear...

Hello Dear... I know that this message will come to you as a surprise. I hoped that you will not expose or betray this trust and confident that I am about to repose on you, my name is M, Shakour Rosarita. I am 19 years old Girl, female, from Tartu Syria, (never married) 61 kg, white in complexion

RE: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410

Original Message Subject: Re: [PATCH v2] dell-laptop: Fix keyboard led max_brightness property for Dell Latitude E6410 From: Darren Hart Date: Wed, October 18, 2017 3:00 pm To: Pali Rohár Cc: Matthew Garrett , Andy Shevchenko , "Gabriel M. Elder" , Gabriel

Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

On Mon, Sep 7, 2015 at 12:28 PM, Chinmay V S wrote: > Thanks for your quick response Mike. > >> Try without the proprietary modules. You may also want to audit futex >> fixes if you can't use a maintained stable tree. 3.2 has a bunch that >> 3.1 does not. > > I see that futex.c has 17 patches in

Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

cheduler (sched_rt.c) on 3.1.10 kernel. > [101640.492840] kernel BUG at kernel/sched_rt.c:1126! > > This turns out to be > 1126 BUG_ON(idx >= MAX_RT_PRIO); The reason for the stack trace is given below. http://www.spinics.net/lists/newbies/msg08889.html -- -- Sujit K M b

[PATCH] ARM: dts: rk3288: pull up cts lines

this patch merely restores them. Suggested-by: Neil Hendin Signed-off-by: Alexandru M Stan --- arch/arm/boot/dts/rk3288.dtsi | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi index 906e938..a059367

[PATCH v2 0/2] ARM: dts: rockchip: pull up cts lines

- CC people with the firefly board - New patch removing redundant pullup code from veyron - cover letter Alexandru M Stan (2): ARM: dts: rockchip: pull up cts lines on rk3288 ARM: dts: rockchip: Remove specific cts pullup from veyron arch/arm/boot/dts/rk3288-veyron.dtsi | 12 arch

[PATCH v2 2/2] ARM: dts: rockchip: Remove specific cts pullup from veyron

With the previous patch ("rk3288: pull up cts lines") this is redundant, I sent that patch for the same reason this existed here, so the lines don't wiggle randomly when disconnected. Signed-off-by: Alexandru M Stan --- Changes in v2: - Restrict changes only to cts pin, leave

[PATCH v2 1/2] ARM: dts: rockchip: pull up cts lines on rk3288

this patch merely restores them. This is similar to what we're already doing with the RX pin, so it should be safe. At worst it might be a slightly higher power usage (through ~50 kohms) when the cts is low. Suggested-by: Neil Hendin Signed-off-by: Alexandru M Stan --- Changes in v2: None

[RFC PATCH v1 13/13] mm: splice local lists onto the front of the LRU

Now that release_pages is scaling better with concurrent removals from the LRU, the performance results (included below) showed increased contention on lru_lock in the add-to-LRU path. To alleviate some of this contention, do more work outside the LRU lock. Prepare a local list of pages to be spli

[RFC PATCH v1 12/13] mm: split up release_pages into non-sentinel and sentinel passes

A common case in release_pages is for the 'pages' list to be in roughly the same order as they are in their LRU. With LRU batch locking, when a sentinel page is removed, an adjacent non-sentinel page must be promoted to a sentinel page to follow the locking scheme. So we can get behavior where ne

[RFC PATCH v1 09/13] mm: introduce add-only version of pagevec_lru_move_fn

For the purposes of this prototype, copy the body of pagevec_lru_move_fn into __pagevec_lru_add so that it can be modified to use the batch locking API while leaving all other callers of pagevec_lru_move_fn unaffected. Signed-off-by: Daniel Jordan --- mm/swap.c | 24 +++- 1 f

[RFC PATCH v1 11/13] mm: use lru_batch locking in release_pages

Introduce LRU batch locking in release_pages. This is the code path where I see lru_lock contention most often, so this is the one I used in this prototype. Signed-off-by: Daniel Jordan --- mm/swap.c | 45 + 1 file changed, 17 insertions(+), 28 deleti

[RFC PATCH v1 07/13] mm: convert to-be-refactored lru_lock callsites to lock-all API

Use the heavy locking API for now to allow us to focus on the path we're measuring to prove the concept--the release_pages path. In that path, LRU batch locking will be used, but everywhere else will be heavy. For now, exclude compaction since this would be a nontrivial refactoring. We can deal

[RFC PATCH v1 08/13] mm: temporarily convert lru_lock callsites to lock-all API

These will use the lru_batch_locks in a later series. Signed-off-by: Daniel Jordan --- mm/swap.c | 18 -- mm/vmscan.c | 4 ++-- 2 files changed, 10 insertions(+), 12 deletions(-) diff --git a/mm/swap.c b/mm/swap.c index c4ca7e1c7c03..cf6a59f2cad6 100644 --- a/mm/swap.c +++ b/

[RFC PATCH v1 10/13] mm: add LRU batch lock API's

Add the LRU batch locking API's themselves. This adds the final piece of infrastructure necessary for locking batches on an LRU list. The API's lock a specific page on the LRU list, taking only the appropriate LRU batch lock for a non-sentinel page and taking the node's/memcg's lru_lock in additi

[RFC PATCH v1 04/13] mm: introduce struct lru_list_head in lruvec to hold per-LRU batch info

Add information about the first and last LRU batches in struct lruvec. lruvec's list_head is replaced with a pseudo struct page to avoid special-casing LRU batch handling at the front or back of the LRU. This pseudo page has its own lru_batch and lru_sentinel fields so that the same code that dea

[RFC PATCH v1 05/13] mm: add batching logic to add/delete/move API's

Change the add/delete/move LRU API's in mm_inline.h to account for LRU batching. Now when a page is added to the front of the LRU, it's assigned a batch number that's used to decide which spinlock in the lru_batch_lock array to take when removing that page from the LRU. Each newly-added page is a

[RFC PATCH v1 02/13] mm: allow compaction to be disabled

This is a temporary hack to avoid the non-trivial refactoring of the compaction code that takes lru_lock in this prototype. This refactoring can be done later. Signed-off-by: Daniel Jordan --- mm/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/mm/Kconfig b/mm/Kconfig index 03ff7703d3

[RFC PATCH v1 01/13] mm: add a percpu_pagelist_batch sysctl interface

From: Aaron Lu --- include/linux/mmzone.h | 2 ++ kernel/sysctl.c| 9 + mm/page_alloc.c| 40 +++- 3 files changed, 50 insertions(+), 1 deletion(-) diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h index 67f2e3c38939..c0552

[RFC PATCH v1 00/13] lru_lock scalability

lru_lock, a per-node* spinlock that protects an LRU list, is one of the hottest locks in the kernel. On some workloads on large machines, it shows up at the top of lock_stat. One way to improve lru_lock scalability is to introduce an array of locks, with each lock protecting certain batches of LR

[RFC PATCH v1 06/13] mm: add lru_[un]lock_all APIs

Add heavy locking API's for the few cases that a thread needs exclusive access to an LRU list. This locks lru_lock as well as every lock in lru_batch_locks. This API will be used often at first, in scaffolding code, to ease the transition from using lru_lock to the batch locking scheme. Later it

[RFC PATCH v1 03/13] mm: add lock array to pgdat and batch fields to struct page

This patch simply adds the array of locks and struct page fields. Ignore for now where the struct page fields are: we need to find a place to put them that doesn't enlarge the struct. Signed-off-by: Daniel Jordan --- include/linux/mm_types.h | 5 + include/linux/mmzone.h | 7 +++ mm/pa

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: > > Hi, > > > > I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b > > makes microblaze unbootable. > > > > I&#x

Re: [PATCH 2/2] send-email: supply a --send-delay=1 by default

f order, which it might well do, since Postfix uses a connection cache to machines that don't do STARTTLS (which, much to my annoyance, vger doesn't offer). In short, I don't think this is going to be especially helpful because it won't change the status quo for a lot of send

Re: [PATCH] mfd: cros ec: spi: Fix "in progress" error signaling

Hello Enric On Mon, Mar 26, 2018 at 9:48 AM, Enric Balletbo Serra wrote: > Dear all, > > Cc'ing some more chromium folks. > > 2017-11-29 13:11 GMT+01:00 Lee Jones : >> On Wed, 27 Sep 2017, Shawn Nematbakhsh wrote: >> >>> For host commands that take a long time to process, cros ec can return >>> e

Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

CONFIG_HIGHMEM=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_MTD=y CONFIG_MTD_TESTS=m CONFIG_MTD_CMDLINE_PARTS=y CONFIG_MTD_BLOCK=y CONFIG_MTD_M25P80=y CONFIG_MTD_SPI_NOR=y

Re: The linux devs can rescind their license grant.

counsel to write a new section for the Copyleft Guide that further explains the irrevocability of GPLv2. We published this when others raised these specious claims back in September. Direct link to new section: https://copyleft.org/guide/comprehensive-gpl-guidech8.html#x11-540007.4 HTH,

[PATCH] tpm: Fix typo in tpmrm class definition

Commit d2e8071bed0be ("tpm: make all 'class' structures const") unfortunately had a typo for the name on tpmrm. Fixes: d2e8071bed0b ("tpm: make all 'class' structures const") Signed-off-by: Justin M. Forbes --- drivers/char/tpm/tpm-chip.c | 2 +- 1

[PATCH v2] tpm: Fix typo in tpmrm class definition

Commit d2e8071bed0be ("tpm: make all 'class' structures const") unfortunately had a typo for the name on tpmrm. Fixes: d2e8071bed0b ("tpm: make all 'class' structures const") Signed-off-by: Justin M. Forbes --- drivers/char/tpm/tpm-chip.c | 2 +- 1

[GIT PATCH] hwmon update against v2.6.23-rc5-git1

region. Signed-off-by: Jean Delvare <[EMAIL PROTECTED]> Signed-off-by: Mark M. Hoffman <[EMAIL PROTECTED]> diff --git a/drivers/hwmon/lm78.c b/drivers/hwmon/lm78.c index 565c4e6..6eea347 100644 --- a/drivers/hwmon/lm78.c +++ b/drivers/hwmon/lm78.c @@ -882,7 +882,7 @@

Re: [PATCH] v3 of IBM power meter driver

bmpex_bmc_data *data) > +{ > + int i, j; > + > + device_remove_file(data->bmc_device, &sensor_dev_attr_name.dev_attr); > + for (i = 0; i < data->num_sensors; i++) > + for (j = 0; j < PEX_NUM_SENSOR_FUNCS; j++) { > +

Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL

On Thursday 27 September 2007, Nick Piggin wrote: > On Saturday 29 September 2007 00:34, Linus Torvalds wrote: > > On Fri, 28 Sep 2007, Nick Piggin wrote: > > > > God I hate select. > > > > > > IMO a better implementation would result in a notification / confirmation > > > of turning on new items,

Re: A bit of kconfig rewrite (Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL)

setup > (e.g. no ARCH=, CROSS_*, *_FLAGS *kbuild* things); > > * checking tool for particular config patterns (for bug reports) > > * system itself must be done with minimum requirements for C libraries > (no ncurses) and tools (no `perl`, no `python`, no `make`). > > > I

Re: [patch 00/20] 2.6.22-stable review

On Mon, Aug 20, 2007 at 11:52:10PM -0700, Greg KH wrote: > This is the start of the stable review cycle for the 2.6.22.5 release. No roll up patch for this one? Justin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majo

WASP for Linux 7?

Expertise: Is there a WASP for Linux 7? What is the accepted and accredited security scanning app for Linux 7--is it SECSCN? Thank you, MS SwRI ISSO/ATA -Original Message- From: linux-audit-boun...@redhat.com [mailto:linux-audit-boun...@redhat.com] On Behalf Of Paul Moore Sent: Monday

loop block-mq conversion scalability issues

The block-mq conversion for loop in 4.0 kernels is showing us an interesting scalability problem with live CDs (ro, squashfs). It was noticed when testing the Fedora beta that the more CPUs a liveCD image was given, the slower it would boot. A 4 core qemu instance or bare metal instance took more

Re: loop block-mq conversion scalability issues

On Fri, 2015-04-24 at 10:59 +0800, Ming Lei wrote: > Hi Justin, > > Thanks for the report. > > On Thu, 23 Apr 2015 16:04:10 -0500 > "Justin M. Forbes" wrote: > > > The block-mq conversion for loop in 4.0 kernels is showing us an > > interesting scal

Re: loop block-mq conversion scalability issues

On Sun, 2015-04-26 at 23:27 +0800, Ming Lei wrote: > Hi Justin, > > On Fri, 24 Apr 2015 16:46:02 -0500 > "Justin M. Forbes" wrote: > > > On Fri, 2015-04-24 at 10:59 +0800, Ming Lei wrote: > > > Hi Justin, > > > > > > Thanks for t

Re: [alsa-devel] [PATCH 1/2] MFD: twl6040: Fix revision information

On 07/17/2012 01:39 AM, Rajeev kumar wrote: diff --git a/sound/soc/codecs/twl6040.c b/sound/soc/codecs/twl6040.c index a36e9fc..2786de2 100644 --- a/sound/soc/codecs/twl6040.c +++ b/sound/soc/codecs/twl6040.c @@ -653,7 +653,7 @@ int twl6040_get_hs_step_size(struct snd_soc_codec *codec) {

You have been pick for a personal donation from me. Email ( leon.hirt...@mail.com ) for more info.‏

-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: NFS mounts failing when keytab present on client

On Tue, 27 Mar 2018, Eric Biggers wrote: > Hi Michael, > > On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote: > > NFS mounts stopped working on one of my computers after a kernel update from > > 4.15.3 to 4.15.4. I traced the problem to the commit > > [46e8d06e423c4f35eac7a8b677b713b3

REF:- INSTRUCTION TO CREDIT YOUR ACCOUNT WITH THE SUM OF (US$10Million)

sincerely, Mr Anthony M. Smith Head Of Account Department, NatWest Bank, London United Kingdom. Here is my private! Email address (bekerb...@gmail.com)

REF:- INSTRUCTION TO CREDIT YOUR ACCOUNT WITH THE SUM OF (US$10Million)

sincerely, Mr Anthony M. Smith Head Of Account Department, NatWest Bank, London United Kingdom. Here is my private! Email address (bekerb...@gmail.com)

RE: [PATCH v2] drm/exynos: Remove dev_err() on platform_get_irq() failure

> -Original Message- > From: Inki Dae > Sent: Wednesday, May 20, 2020 11:08 AM > To: Tamseel Shams ; jy0922.s...@samsung.com; > sw0312@samsung.com; kyungmin.p...@samsung.com; airl...@linux.ie; > dan...@ffwll.ch > Cc: dri-de...@lists.freedesktop.org; linux-arm-ker...@lists.infradead.

Re: [RFC PATCH v2 1/3] add mikrobus descriptors to greybus_manifest

Hi, Trying to add more information regarding the newly added descriptors and describe how they are used now within the mikroBUS driver. On Tue, Aug 18, 2020 at 6:18 PM Vaishnav M A wrote: > > This patch adds new descriptors used in the manifest parsing inside > the mikrobus driver, t

Re: [PATCH 0/3] PWM backlight interpolation adjustments

les changed, 42 insertions(+), 42 deletions(-) > > -- > 2.27.0 > Hello, Friendly ping. Let me know if you would like me to make any changes to my patches. Thanks, Alexandru M Stan

[RFC PATCH v2 2/3] mikroBUS driver for add-on boards on mikrobus ports

boards are available here: https://github.com/vaishnav98/manifesto/tree/mikrobusv3 Signed-off-by: Vaishnav M A --- MAINTAINERS | 6 + drivers/misc/Kconfig | 1 + drivers/misc/Makefile | 1 + drivers/misc/mikrobus/Kconfig

[RFC PATCH v2 0/3] mikroBUS driver for add-on boards

, use greybus CPort protocol enum instead of new protcol enums Fix cases of wrong indendation, ignoring return values, freeing allocated resources in case of errors and other style suggestions in v1 review. Vaishnav M A (3): add mikrobus descriptors to greybus_manifest

[RFC PATCH v2 3/3] Add Device Tree Bindings for mikroBUS port

This patch adds device tree bindings for the mikroBUS port, device tree overlays for the mikrobus Port on the BeagleBoard.org PocketBeagle is available here : github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-MIKROBUS-0.dts Signed-off-by: Vaishnav M A --- .../bindings/misc/linux

[RFC PATCH v2 1/3] add mikrobus descriptors to greybus_manifest

drivers through the Unified Properties API under linux/property.h The corresponding pull request for manifesto is updated at : https://github.com/projectara/manifesto/pull/2 Signed-off-by: Vaishnav M A --- include/linux/greybus/greybus_manifest.h | 47 1 file changed, 47

Re: [greybus-dev] [RFC PATCH v2 3/3] Add Device Tree Bindings for mikroBUS port

On Tue, Aug 18, 2020 at 7:05 PM Laurent Pinchart wrote: > > Hi Vaishnav, > > Thank you for the patch. > > On Tue, Aug 18, 2020 at 06:18:15PM +0530, Vaishnav M A wrote: > > This patch adds device tree bindings for the mikroBUS port, > > device tree overlay

Re: [RFC PATCH v2 0/3] mikroBUS driver for add-on boards

On Tue, Aug 18, 2020 at 8:54 PM Greg KH wrote: > > On Tue, Aug 18, 2020 at 06:18:12PM +0530, Vaishnav M A wrote: > > Hi, > > > > This Patch series is an update to the mikroBUS driver > > RFC v1 Patch : https://lkml.org/lkml/2020/7/24/518 . > > Please use lore.k

Re: [RFC PATCH v2 0/3] mikroBUS driver for add-on boards

et_maintainer.pl after making the changes will add both recipients in future versions. Thanks and Regards, Vaishnav M A > > On 2020-08-18 07:48, Vaishnav M A wrote: > > Hi, > > > > This Patch series is an update to the mikroBUS driver > > RFC v1 Patch : https://lkml.org

Re: [PATCH] arm64: dts: qcom: Clean up sc7180-trogdor voltage rails

t;1984000>; > regulator-initial-mode = ; > }; > > @@ -491,21 +438,6 @@ pp1200_l3c: ldo3 { > regulator-initial-mode = ; > }; > > - ld_pp1800_esim_l4c: > - vddpx_5: > - pp1800_l4c: ldo4 { > - regulator-min-microvolt = <1648000>; > - regulator-max-microvolt = <3304000>; > - regulator-initial-mode = ; > - }; > - > - vddpx_6: > - pp1800_l5c: ldo5 { > - regulator-min-microvolt = <180>; > - regulator-max-microvolt = <180>; > - regulator-initial-mode = ; > - }; > - > vddpx_2: > ppvar_l6c: ldo6 { > regulator-min-microvolt = <180>; > -- > 2.29.2.576.ga3fc446d84-goog > Reviewed-by: Alexandru M Stan

Re: [PATCH] spi: spi-geni-qcom: Use the new method of gpio CS control

7;output-enable' pinctrl > setting. > > Cc: Akash Asthana > Cc: Bjorn Andersson > Reviewed-by: Douglas Anderson > Acked-by: Alexandru M Stan I meant this as a joke in chat. It doesn't really mean anything in any capacity. > Signed-off-by: Stephen Boyd > --- >

Re: [dm-devel] [PATCH 1/1] block: rework flush sequencing for blk-mq

On 03/14/2014 02:13 PM, Mike Snitzer wrote: > Yeah, not sure why single path scsi_debug "just works", maybe it is a > "feature" of the older multipathd I have kicking around?, but for basic > data path testing scsi_debug is a quick means to an end. I can look > closer at _why_ it gets multipathd i

From: Joseph

I am a US Army officer currently on military assignment in Iraq, I humbly ask of your assistance secure and invest some money for me in your country. As a matter of fact, I have the sum of US$5 Million which I would like you to help me to invest. I will appreciate it if you can assist me urgent

X509_CERTIFICATE_PARSER depends on SYSTEM_TRUSTED_KEYRING

öllig wurscht, was heut beschlos- | M G Berberich sen wird: I bin sowieso dagegn!“ | berbe...@fmi.uni-passau.de (SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

[PATCH] cciss: return 0 from driver probe function on success, not 1

From: Stephen M. Cameron A return value of 1 is interpreted as an error Signed-off-by: Stephen M. Cameron --- drivers/block/cciss.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index edfa251..0c004ac 100644 --- a

[PATCH] cciss: return 0 from driver probe function on success, not 1

From: Stephen M. Cameron A return value of 1 is interpreted as an error. See pci_driver. in local_pci_probe(). If you're wondering how this ever could have worked, it's because it used to be the case that only return values less than zero were interpreted as failure. But even in t

[PATCH] cciss: return 0 from driver probe function on success, not 1

Just resending the patch with a better change log message (as requested by Andrew Morton) and cc'ing sta...@vger.kernel.org, (as I originally had intended.) --- Stephen M. Cameron (1): cciss: return 0 from driver probe function on success, not 1 drivers/block/cciss.c |2 +- 1

[PATCH] PCI: warn on driver probe return value greater than zero

From: Stephen M. Cameron Ages ago, drivers could return values greater than zero from their probe function and this would be regarded as success. Commit f3ec4f87d607f40497 "PCI: change device runtime PM settings for probe and remove" slightly altered this in 2010,

Re: [RFC][glibc PATCH] fcntl-linux.h: add new definitions and manual updates for open file description locks

@@ -2890,7 +2894,7 @@ Get flags associated with the open file. @xref{File Status Flags}. Set flags associated with the open file. @xref{File Status Flags}. @item F_GETLK -Get a file lock. @xref{File Locks}. +Test a file lock. @xref{File Locks}. F_GETLK does get the (first) l

Re: [RFC][glibc PATCH] fcntl-linux.h: add new definitions and manual updates for open file description locks

> Likewise. You infact write that it does get the lock information > later in the document wrt. F_OFD_GETLK. Sorry, I disagree here...GETLK is really a misnomer, IMO. TESTLK would have been a better name. GETLK are used is to "get the first lock". It's a way to test whether a

Re: [PATCH 2/7] staging: unisys: move uislib/platform proc entry to debugfs

en Romer | Software Engineer | Virtual Systems Development Unisys Corporation | 2476 Swedesford Rd | Malvern, PA 19355 | 610-648-7140 N�r��yb�X��ǧv�^�)޺{.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~i���z��w���?�&�)ߢf��^jǫy�m��@A�a��� 0��h���i

Re: [PATCH 2/7] staging: unisys: move uislib/platform proc entry to debugfs

On Tue, 2014-05-20 at 10:09 +0900, Greg KH wrote: > On Mon, May 19, 2014 at 10:57:08PM +0300, Dan Carpenter wrote: > > On Mon, May 19, 2014 at 09:42:22AM -0500, Romer, Benjamin M wrote: > > > On Sun, 2014-05-18 at 09:49 -0700, Greg KH wrote: > > > > Also, why are thes

[PATCH] Fix flags for initramfs LZ4 compression

initramfs is junk. Signed-off-by: Daniel M. Weeks --- scripts/gen_initramfs_list.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/gen_initramfs_list.sh b/scripts/gen_initramfs_list.sh index ef47409..17fa901 100644 --- a/scripts/gen_initramfs_list.sh +++ b/scripts

[PATCH] initramfs: Debug detected compression method

This can greatly aid in narrowing down the real source of initramfs problems such as failures related to the compression of the in-kernel initramfs when an external initramfs is in use as well. Existing errors are ambiguous as to which initramfs is a problem and why. Signed-off-by: Daniel M

Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP

On Tue, 2014-04-08 at 10:53 +0800, Fengguang Wu wrote: > Hi Benjamin, > > > Fengguang, > > > > I ran your script against freshly-checked-out source from staging-next, and > > was not able to reproduce the error with it. My boot log is attached. I > > noticed that your log did not have "Hypervis

[PATCH] unisys: staging: Check for s-Par firmware before initializing s-Par modules

_t bufsize); struct seq_file *visor_seq_file_new_buffer(void *buf, size_t buf_size); void visor_seq_file_done_buffer(struct seq_file *m); +int is_spar_system( void ); #endif diff --git a/drivers/staging/unisys/uislib/uislib.c b/drivers/staging/unisys/uislib/uislib.c index 8ea9c46..aa60ccb 100644 ---

Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP

On Wed, 2014-04-09 at 16:10 -0700, H. Peter Anvin wrote: > On 04/09/2014 04:01 PM, Fengguang Wu wrote: > > CC the KVM people: it looks like a KVM problem that can be triggered by > > > > qemu-system-x86_64 -cpu Haswell,+smep,+smap > > I'm really confused. First of all, is this a KVM prob

Re: [PATCH] unisys: staging: Check for s-Par firmware before initializing s-Par modules

On Wed, 2014-04-09 at 12:25 -0700, Greg Kroah-Hartman wrote: > Patches need to do only one thing, so can you please split this up in to > multiple patches, each one only doing one thing. Sorry about that! I'll send another patch that fixes all of the copyright statements at once then. :) > You fo

[PATCH] staging: unisys: fix copyright notices

This patch replaces the inconsistent copyright symbols in each source file with (C). Signed-off-by: Benjamin Romer --- drivers/staging/unisys/channels/channel.c | 2 +- drivers/staging/unisys/channels/chanstub.c | 2 +- drivers/staging/u

RE: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error

> -Original Message- > From: Fujinaka, Todd [mailto:todd.fujin...@intel.com] > Sent: Thursday, April 10, 2014 7:59 AM > To: Borislav Petkov; e1000-de...@lists.sourceforge.net > Cc: net...@vger.kernel.org; lkml > Subject: Re: [E1000-devel] e1000e :00:19.0 eth0: Hardware Error > > We als

SUSPECT: General web-mail maintenance

General web-mail maintenance Dear Account Owner, THIS MESSAGE IS DIRECTED TO THOSE USING Office Outlook Web Access Web-mail (2007 version). We want to upgrade all Microsoft Exchange email account scheduled for today as part of our duty to strengthen security of your mailbox. CLICK HERE

Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP

On Thu, 2014-04-10 at 19:28 -0700, H. Peter Anvin wrote: > On 04/10/2014 06:19 AM, Romer, Benjamin M wrote: > > > > I'm confused by the intended behavior of KVM.. Is the intention of the > > -cpu switch to fully emulate a particular CPU? If that's the case, the >

Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP

On Fri, 2014-04-11 at 10:40 -0700, H. Peter Anvin wrote: > On 04/11/2014 10:35 AM, Jet Chen wrote: > > > > As Peter said, QEMU probably should *not* set the hypervisor bit. But based > > on my testing, I think KVM works properly in this case. > > > > Either way, unless there is a CPUID interfac

Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP

On Sat, 2014-04-12 at 01:35 +0800, Jet Chen wrote: > Hi Ben, > > I re-tested this case with/without option -enable-kvm. > > qemu-system-x86_64 -cpu Haswell,+smep,+smap invalid op > qemu-system-x86_64 -cpu kvm64 invalid op > qemu-system-x86_64 -cp

[PATCH] i2c: piix4: Continue probing for auxiliary SMBus without main

Some BIOS may only allow access to the AMD auxiliary SMBus - reserving the main SMBus for system functions only. Probing should continue even if the main bus is not available so at least the auxiliary can be added. Signed-off-by: Daniel M. Weeks --- This patch may warrant some discussion. I ran

Re: [PATCH v6 0/6] add cpuidle support for Exynos5420

>> >>>>> >>>>> For the whole series, >>>>> >>>>> Reviewed-by: Tomasz Figa >>>> >>>> >>>> Thanks Tomasz. >>>> >>>> Dear Kukjin, >>>> Can you take these patches. >>

Re: [linux-lvm] copying file results in out of memory, kills other processes, makes system unavailable

On Sat, Jun 14, 2014 at 08:13:39PM +0930, David Newall wrote: > I'm running a qemu virtual machine, 2 x i686 with 2GB RAM. VM's disks are > managed via LVM2. Most disk activity is on one LV, formatted as ext4. > Backups are taken using snapshots, and at the time of the problem that I am > about t

Greetings

I am a US Army officer currently on military assignment in Iraq, I humbly ask of your assistance secure and invest some money for me in your country. As a matter of fact, I have the sum of US$5 Million which I would like you to help me to invest. I will appreciate it if you can assist me urgentl

Re: An example of prideful GPL violators who do their violating out in the open

ast time we discussed it, but I'm open-minded to reconsider if any Linux copyright holders would like the GPL Compliance Project for Linux Developers to do prioritize this violation. They know how to reach me. -- Bradley M. Kuhn, Executive Director, Software Freedom Conservancy (home of

Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance

On Fri, 2014-09-05 at 14:52 +0530, Sudip Mukherjee wrote: > fixed sparse warning : context imbalance in 'pause_device' > unexpected unlock > this patch will generate warning from checkpatch for > lines over 80 character , but since those are user-visible strings > so it was

Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance

On Mon, 2014-09-08 at 21:57 +0530, Sudip Mukherjee wrote: > Hi Ben, > thanks. the same file is having two more similar warnings. if you want i can > resend a patch fixing all the three warnings , or i can send two separate > patches. > I personally will prefer two separate patches , as that will b

Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance

On Mon, 2014-09-08 at 22:08 +0530, Sudip Mukherjee wrote: > Hi Ben, > sorry to disturb you again. i got confused , which one is perfect one > combined patch or > separate patches? > > thanks > sudip Two patches, as you preferred. -- Ben

Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance

Should I do this instead of Tested-by and Signed-off-by, in the future? -- Ben N�r��yb�X��ǧv�^�)޺{.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~i���z��w���?�&�)ߢf��^jǫy�m��@A�a��� 0��h���i

Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance

On Mon, 2014-09-08 at 10:24 -0700, Greg Kroah-Hartman wrote: > If you test it, do a tested-by. > > If you sign off on it (i.e. it flows through you to me), then a > signed-off is correct. > > Hope this helps, > > greg k-h It does. :) We should add the Tested-by then, too. Acked-by: Benjamin Ro

Re: [PATCH] staging: unisys: uislib: uislib.c: sparse warning of context imbalance

isible strings > so it was not modified. > > Signed-off-by: Sudip Mukherjee I tested your changes, and this patch works fine. Thanks! -- Ben Acked-by: Benjamin Romer Tested-by: Benjamin Romer N�r��yb�X��ǧv�^�)޺{.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~����i��

Re: [PATCH v2 01/11] crypto: Documentation - crypto API high level spec

Hi Stephan, Great docs! I think they will be very useful! Thanks! I only have 2 comments below. regards, Joy On Sun, 2014-11-02 at 21:35 +0100, Stephan Mueller wrote: > The design of the kernel crypto API as well as hints to program with > the kernel crypto API are given. > > The documentation

Re: [PATCH v2 02/11] crypto: Documentation - userspace interface spec

Hi Stephan, On Sun, 2014-11-02 at 21:36 +0100, Stephan Mueller wrote: > The userspace interface of the kernel crypto API is documented with > * a general explanation > * a discussion of the memory in-place operation > * the description of the message digest API > * the description of the symme

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