ptrace Makefile doesn't have an explicit build rule. As a result,
ptrace build fails, when it is run from top level Makefile target
kselftest. Without the explicit rule, make works only when it is
run in the current directory or from selftests directory. Add an
explicit build rule to fix the
On Tue, Mar 10, 2015 at 3:52 PM, Arnd Bergmann wrote:
> On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
>> > The top level qcom,msm-id and qcom,board-id are utilized by
>> > bootloaders
>> >> on Qualcomm MSM platforms to determine which device tree should be
>>
ptrace, efivars, and kcmp Makefiles don't have explicit build rule.
As a result, build fails when make is run from top level Makefile
target kselftest. Without the explicit rule, make works only when
it is run in the current directory or from selftests directory.
Fxing the problems by adding an
efivars Makefile doesn't have an explicit build rule. As a result,
efivars build fails, when it is run from top level Makefile target
kselftest. Without the explicit rule, make works only when it is
run in the current directory or from selftests directory. Add an
explicit build rule to fix the
kcmp Makefile doesn't have an explicit build rule. As a result,
kcmp build fails, when it is run from top level Makefile target
kselftest. Without the explicit rule, make works only when it is
run in the current directory or from selftests directory. Add an
explicit build rule to fix the problem.
On Tue, 10 Mar 2015 21:31:58 +0100
> > Probably a PCMCIA not a block layer change - well I guess could be
> > either. I fixed a pile of PCMCIA bugs and also reworked the allocator for
> > pure PCI boxes so it didn't do various bad things.
> >
> > Can you tweak drivers/pcmcia/Kconfig for config
Hi Joe,
On Tue, Mar 10, 2015 at 10:50 PM, Joe Perches wrote:
> On Tue, 2015-03-10 at 22:34 +0100, Geert Uytterhoeven wrote:
>> Gcc < 4.3 doesn't understand binary constants (0b*):
>
> trivia:
>
>> diff --git a/drivers/staging/fbtft/fb_hx8340bn.c
>> b/drivers/staging/fbtft/fb_hx8340bn.c
> []
>>
On Tue, 2015-03-10 at 22:34 +0100, Geert Uytterhoeven wrote:
> Gcc < 4.3 doesn't understand binary constants (0b*):
trivia:
> diff --git a/drivers/staging/fbtft/fb_hx8340bn.c
> b/drivers/staging/fbtft/fb_hx8340bn.c
[]
> @@ -156,10 +156,10 @@ static int set_var(struct fbtft_par *par)
> static
On Tue, Mar 10, 2015 at 04:14:17PM +0100, Alexander Bergmann wrote:
> Hi Herbert,
>
> I just fixed a small DRBG return code issue inside testmgr.c directly
> related to the RNG changes Stephan submitted.
Thanks Alex. Could you resend this via linux-cry...@vger.kernel.org
so that patchworks can
Hi Dave,
On Mon, 09 Mar 2015 23:43:29 -0400 (EDT) David Miller
wrote:
>
> From: Stephen Rothwell
> Date: Tue, 10 Mar 2015 12:08:42 +1100
>
> > Today's linux-next merge of the net-next tree got a conflict in
> > drivers/net/ethernet/cadence/macb.c between commit 0b2eb3e9bc73 ("net:
> > macb:
Hi,
As per the subject, avoid evaluating ACPI_HANDLE() if we can as that one is
rather costly.
Kind regards,
Rafael
--
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
From: Rafael J. Wysocki
If dev is NULL in __gpiod_get_index() and both ACPI and OF are
enabled, it will be checked twice before the code decides to give
up with DT/ACPI lookup, so avoid that.
Also use the observation that ACPI_COMPANION() is much more efficient
than ACPI_HANDLE(), because the
From: Rafael J. Wysocki
In acpi_gpiochip_request_interrupts() the handle local
variable already contains the value that we want to pass
to acpi_walk_resources(), so it is better to use that
variable instead of evaluating ACPI_HANDLE() once more
for the same device.
Signed-off-by: Rafael J.
On Tue, Mar 10, 2015 at 10:41:09PM +0100, Alexandre Belloni wrote:
> On 10/03/2015 at 16:23:53 -0500, Felipe Balbi wrote :
> > > Yeah, let's drop it for now but I have the feeling that this will
> > > break (I actually broke it when switching at91 to multiplatform).
> >
> > aha, that changes it.
On 10/03/2015 at 16:23:53 -0500, Felipe Balbi wrote :
> > Yeah, let's drop it for now but I have the feeling that this will
> > break (I actually broke it when switching at91 to multiplatform).
>
> aha, that changes it. So you already have something which makes this
> break ? Are you planning on
[+cc Rob, Yijing]
On Mon, Mar 09, 2015 at 05:38:05PM -0700, Ray Jui wrote:
> This adds the support for Broadcom iProc PCIe controller
>
> pcie-iproc.c servers as the common core driver, and front-end bus
> interface needs to be added to support different bus interfaces
>
> pcie-iproc-pltfm.c
On Tue, Mar 10, 2015 at 07:59:21PM +0800, Chen-Yu Tsai wrote:
> This patch adds the AXP221 regulators. Only the ones directly used
> on the board are added.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
drivers/staging/fbtft/fb_hx8340bn.c:160:3: error: invalid suffix "b111" on
integer constant
...
Hence use hexadecimal constants (0x*) instead.
Signed-off-by: Geert Uytterhoeven
---
This is against v4.0-rc3. In next-20150310 there are two whitespace
differences.
---
drivers/staging/f
On Tue, Mar 10, 2015 at 07:59:24PM +0800, Chen-Yu Tsai wrote:
> The Hummingbird A31 has an AMPAK AP6210 WiFi+Bluetooth module. The
> WiFi part is a BCM43362 IC connected to MMC1 in the A31 SoC via SDIO.
> The IC also takes a power enable signal via GPIO. This is supported
> with the new power
On Tue, Mar 10, 2015 at 07:59:22PM +0800, Chen-Yu Tsai wrote:
> mmc1 is used to connect to the WiFi chip on the Hummingbird A31.
>
> Signed-off-by: Chen-Yu Tsai
> ---
> arch/arm/boot/dts/sun6i-a31.dtsi | 8
> 1 file changed, 8 insertions(+)
>
> diff --git
Hi,
On 09/03/2015 at 15:30:01 +0100, Rafael J. Wysocki wrote :
> > > > Actaully, your platform should just refuse to enter suspend-to-RAM
> > > > when hw watchdog is enabled.
> > >
> > > Quite likely, depending on how exactly the suspend is implemented.
> > >
> >
> > We've had absolutely zero
On Sun, Feb 22, 2015 at 12:25:35PM +0800, Sneeker Yeh wrote:
> These patches add support for XHCI compliant Host controller found
> on Fujitsu Socs, and are based on http://lwn.net/Articles/629162/
> The first patch is to add Fujitsu glue layer of Synopsis DesignWare USB3
> driver
> and last four
On Tue, Mar 10, 2015 at 05:02:20PM -0400, Jiri Kosina wrote:
> On Tue, 10 Mar 2015, Josh Poimboeuf wrote:
>
> > Just an update on the status of this RFC. Thanks to everybody for all
> > the useful comments. I plan to incorporate the resulting changes in an
> > eventual v2 of this patch set.
>
On Tue, Mar 10, 2015 at 07:59:13PM +0800, Chen-Yu Tsai wrote:
> The Hummingbird A31 has an AXP221 PMIC hooked up to the P2WI controller.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
On Tue, Mar 10, 2015 at 07:59:12PM +0800, Chen-Yu Tsai wrote:
> From: Boris BREZILLON
>
> The p2wi controller has only one possible pinmux setting. Use it by
> default in the dtsi, instead of having to set it in each board's dts.
>
> Signed-off-by: Boris BREZILLON
> [w...@csie.org: reformat
On Tue, Mar 10, 2015 at 3:19 PM, Arnd Bergmann wrote:
> On Tuesday 10 March 2015 16:28:44 Maxime Coquelin wrote:
>> 2015-03-10 16:00 GMT+01:00 Arnd Bergmann :
>> > On Friday 20 February 2015 19:01:04 Maxime Coquelin wrote:
>> >> Some platforms need to initialize the reset controller before the
On Tue, Mar 10, 2015 at 07:59:16PM +0800, Chen-Yu Tsai wrote:
> The Hummingbird A31 has an AXP221 PMIC hooked up to the
> P2WI controller.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
Signed-off-by: Marek Belisko
---
drivers/power/twl4030_madc_battery.c | 81
1 file changed, 81 insertions(+)
diff --git a/drivers/power/twl4030_madc_battery.c
b/drivers/power/twl4030_madc_battery.c
index 6af28b5..4bcb4a9 100644
---
Without MODULE_ALIAS twl4030_madc_battery won't get loaded automatically.
Signed-off-by: Marek Belisko
---
drivers/power/twl4030_madc_battery.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/power/twl4030_madc_battery.c
b/drivers/power/twl4030_madc_battery.c
index 3e0005d..d0753f1
When twl_4030_madc_battery is build as module, MODULE_DEVICE_TABLE allow
the module to be auto-loaded since the module will match the devices
instantiated from device tree.
Signed-off-by: Marek Belisko
---
drivers/power/twl4030_madc_battery.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Because of added iio error handling private data allocation was converted
to managed to simplify code.
Signed-off-by: Marek Belisko
Reviewed-By: Sebastian Reichel
---
drivers/power/twl4030_madc_battery.c | 99 +++-
1 file changed, 64 insertions(+), 35
This patches adding support for twl4030_madc_battery to use twl4030_madc iio
framework + DT support.
Patches was tested on gta04 board. twl4030_madc_battery driver is converted in
first patch to iio consumer and in next patches is added support for devicetree
+ some small fixes for module
Signed-off-by: Marek Belisko
---
.../bindings/power_supply/twl4030_madc_battery.txt | 43 ++
1 file changed, 43 insertions(+)
create mode 100644
Documentation/devicetree/bindings/power_supply/twl4030_madc_battery.txt
diff --git
Added battery support for gta04 devices.
Signed-off-by: Marek Belisko
---
arch/arm/boot/dts/omap3-gta04.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi
b/arch/arm/boot/dts/omap3-gta04.dtsi
index fb3a696..cbf515a 100644
On Tue, Mar 10, 2015 at 10:21:22PM +0100, Alexandre Belloni wrote:
> On 10/03/2015 at 15:53:12 -0500, Felipe Balbi wrote :
> > On Tue, Mar 03, 2015 at 10:41:38AM +0100, Alexandre Belloni wrote:
> > > On 03/03/2015 at 09:26:20 +0100, Boris Brezillon wrote :
> > > > > config USB_ATMEL_USBA
> > > >
On 10/03/2015 at 15:53:12 -0500, Felipe Balbi wrote :
> On Tue, Mar 03, 2015 at 10:41:38AM +0100, Alexandre Belloni wrote:
> > On 03/03/2015 at 09:26:20 +0100, Boris Brezillon wrote :
> > > > config USB_ATMEL_USBA
> > > > tristate "Atmel USBA"
> > > > - depends on AVR32 || ARCH_AT91
2015-03-10 21:21 GMT+01:00 Arnd Bergmann :
> On Tuesday 10 March 2015 16:44:24 Maxime Coquelin wrote:
>> 2015-03-10 16:02 GMT+01:00 Arnd Bergmann :
>> > On Friday 20 February 2015 19:01:06 Maxime Coquelin wrote:
>> >> +/* AHB1 */
>> >> +#define GPIOA_RESET0
>> >> +#define GPIOB_RESET1
>>
On 10/03/2015 at 13:02:09 -0700, Brian Norris wrote :
> On Tue, Mar 10, 2015 at 10:02:15AM +0100, Arnd Bergmann wrote:
> > I actually added a bunch of these in other places, but have stopped
> > doing so because Russell didn't like them, and I tend to follow
> > his argument now that it's actually
On Sun, Mar 08, 2015 at 02:35:25PM -0400, Alan Stern wrote:
> On Sun, 8 Mar 2015, Al Viro wrote:
>
> > On Sat, Mar 07, 2015 at 04:08:49PM -0500, Alan Stern wrote:
> > > On Sat, 7 Mar 2015, Alexander Holler wrote:
> > >
> > > > Am 07.03.2015 um 12:23 schrieb Alexander Holler:
> > > > > Am
Hi Bjorn,
On 3/10/2015 1:56 PM, Bjorn Helgaas wrote:
> On Mon, Mar 09, 2015 at 05:38:03PM -0700, Ray Jui wrote:
>> Export symbols of the following PCI functions so they can be referenced
>> by a PCI driver compiled as a kernel loadable module:
>>
>> pci_common_swizzle
>> pci_create_root_bus
>>
On Tue, 10 Mar 2015, Josh Poimboeuf wrote:
> Just an update on the status of this RFC. Thanks to everybody for all
> the useful comments. I plan to incorporate the resulting changes in an
> eventual v2 of this patch set.
>
> But, as Peter and Ingo have pointed out, stack traces are indeed
>
On Tuesday 10 March 2015, Brian Norris wrote:
> On Tue, Mar 10, 2015 at 05:48:37PM +0100, Arnd Bergmann wrote:
> > The cfi_staa_write_buffers function uses a large amount of kernel stack
> > whenever CONFIG_MTD_MAP_BANK_WIDTH_32 is set, and that results in a
> > warning on ARM allmodconfig builds:
Update with the same contact information found in the README from the
linux-firmware tree.
Cc: David Woodhouse
Cc: Ben Hutchings
Signed-off-by: Bruce Allan
---
firmware/README.AddingFirmware |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Greg,
On Tue, 10 Mar 2015 16:08:15 +0100 Greg KH wrote:
>
> Sorry about that. Yes, I know it's a mess. The build error on ppc
> should now be fixed in my tree. The build warnings are still there
> (some are gone). I should just go fix them up myself, and will do so
> tonight if I don't
On Mon, Mar 09, 2015 at 05:38:03PM -0700, Ray Jui wrote:
> Export symbols of the following PCI functions so they can be referenced
> by a PCI driver compiled as a kernel loadable module:
>
> pci_common_swizzle
> pci_create_root_bus
> pci_stop_root_bus
> pci_remove_root_bus
>
On Tue, Mar 03, 2015 at 10:41:38AM +0100, Alexandre Belloni wrote:
> On 03/03/2015 at 09:26:20 +0100, Boris Brezillon wrote :
> > > config USB_ATMEL_USBA
> > > tristate "Atmel USBA"
> > > - depends on AVR32 || ARCH_AT91
> > > + depends on AVR32 || ARCH_AT91 && COMMON_CLK_AT91
> >
> > I guess
On Tue, Mar 10, 2015 at 04:12:33PM -0400, Adrian Remonda wrote:
> renamed:Documentation/spi/spidev_test.c -> tools/spi/spidev_test.c
>
> Signed-off-by: Adrian Remonda
> ---
> Documentation/spi/spidev_test.c | 318
> ---
> tools/spi/spidev_test.c
On Tue, Mar 10, 2015 at 04:12:31PM -0400, Adrian Remonda wrote:
>
> Signed-off-by: Adrian Remonda
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Mar 10, 2015 at 9:06 PM, Andy Lutomirski wrote:
>> .ss1 also seems to be a write-only field:
>>
>> $ grep -r '[.>]ss1' .
>> ./include/asm/processor.h: if (unlikely(tss->x86_tss.ss1 !=
>> thread->sysenter_cs)) {
>
> This is a read :)
You are right.
>> ./include/asm/processor.h:
On Tue, Mar 10, 2015 at 04:12:32PM -0400, Adrian Remonda wrote:
> Now it is possible to send string and hexadecimal data as an input
> parameter
>
> v2: Fixed coding style and removed unnecessary castings from malloc
> Noted by Mark Brown
>
> modified:
On Tue, Mar 10, 2015 at 04:12:30PM -0400, Adrian Remonda wrote:
> v2: Fixed coding style and removed unnecessary castings
> As noted by Geert Uytterhoeven and Mark Brown
>
> modified: Documentation/spi/spidev_test.c
Applied, thanks, but please follow the process in
On Tue, Mar 10, 2015 at 03:00:49AM +, Peter Chen wrote:
>
> > On Tue, Mar 10, 2015 at 02:02:44AM +, Peter Chen wrote:
> > >
> > > > > --- a/drivers/usb/gadget/udc/lpc32xx_udc.c
> > > > > +++ b/drivers/usb/gadget/udc/lpc32xx_udc.c
> > > > > @@ -1803,7 +1803,7 @@ static int
On Tue, Mar 10, 2015 at 02:53:17PM +0200, Ivan T. Ivanov wrote:
>
> On Tue, 2015-03-10 at 11:06 +, Mark Brown wrote:
> > I'm sorry but I can't parse the above. What does "they could issue
> > setup method" mean and why is it a problem?
> Client drivers could execute spi_setup() in probe(),
On Tue, Mar 10, 2015 at 10:08:48AM -0700, Mitchel Humpherys wrote:
> Clients often get confused when ion_phys errors out due to some heap
> being used that they didn't expect. Add the heap name and heap type to
> the error message to make it more obvious.
>
> Signed-off-by: Mitchel Humpherys
Fix set but not used warning.
Signed-off-by: Fabian Frederick
---
fs/udf/balloc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/udf/balloc.c b/fs/udf/balloc.c
index 1ba2baa..02948f0 100644
--- a/fs/udf/balloc.c
+++ b/fs/udf/balloc.c
@@ -358,7 +358,6 @@ static void
else after return is not needed.
Signed-off-by: Fabian Frederick
---
fs/udf/balloc.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/fs/udf/balloc.c b/fs/udf/balloc.c
index 30f4641..1cd8916 100644
--- a/fs/udf/balloc.c
+++ b/fs/udf/balloc.c
@@ -63,15 +63,14
udf_readdir(), udf_find_entry() and udf_pc_to_char() use
udf_get_filename to obtain name length. Give that function
an appropriate name.
Signed-off-by: Fabian Frederick
---
fs/udf/dir.c | 3 ++-
fs/udf/namei.c | 3 ++-
fs/udf/symlink.c | 7 ---
fs/udf/udfdecl.h | 4 ++--
buffer_head.h was already included in udfdecl.h
Signed-off-by: Fabian Frederick
---
fs/udf/balloc.c| 1 -
fs/udf/dir.c | 1 -
fs/udf/directory.c | 1 -
fs/udf/file.c | 1 -
fs/udf/inode.c | 1 -
fs/udf/misc.c | 1 -
fs/udf/namei.c | 1 -
fs/udf/partition.c | 1 -
udf_bitmap_prealloc_blocks() can only return positive value and is only
used to assign sector_t allocated.
Signed-off-by: Fabian Frederick
---
fs/udf/balloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/udf/balloc.c b/fs/udf/balloc.c
index 02948f0..30f4641 100644
---
On Tuesday, March 10, 2015 9:10 AM, Ian Abbott wrote:
> "comedidev.h" includes PCI-specific stuff that gets included by all
> comedi drivers including non-PCI ones. Separate it out into its own
> header "comedi_pci.h". Make the new header include and
> "comedidev.h" so that comedi PCI drivers
On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote:
> On Sat, 28 Feb 2015 00:08:52 +0100
> Pavel Machek wrote:
>
> > Hi!
> >
> > It seems that pcmcia was unhappy even before, but eject definitely
> > oopsed it.
> >
> > Any ideas?
>
> Probably a PCMCIA not a block layer change - well I
On Tue, 2015-03-10 at 12:58 -0700, Brian Norris wrote:
> On Tue, Mar 10, 2015 at 11:33:36AM -0700, Joe Perches wrote:
> > On Tue, 2015-03-10 at 17:51 +0100, Arnd Bergmann wrote:
> > > As the only comments I got for the "mtd: cfi: reduce stack size"
> > > patch were about whitespace changes, it
On Wednesday 25 February 2015 16:24:06 Arun Ramamurthy wrote:
> >>> Should I run this by Alan Stern?
> >>
> >> I've added him to Cc here. He clearly didn't know the background about
> >> the DT binding change, and should not need to, but he may have an opinion
> >> on what names we should use.
>
Documented the return values of KVA mapping functions,
pud_set_huge(), pmd_set_huge, pud_clear_huge() and
pmd_clear_huge().
Simplified the conditions to select HAVE_ARCH_HUGE_VMAP
in Kconfig since X86_PAE depends on X86_32.
There is no functinal change in this patch.
Signed-off-by: Toshi Kani
This patchset enhances MTRR checks for the kernel huge I/O mapping,
which was enabled by the patchset below:
https://lkml.org/lkml/2015/3/3/589
The following functional changes are made in patch 3/3.
- Allow pud_set_huge() and pmd_set_huge() to create a huge page
mapping to a range covered
When an MTRR entry is inclusive to a requested range, i.e.
the start and end of the request are not within the MTRR
entry range but the range contains the MTRR entry entirely,
__mtrr_type_lookup() ignores such case because both
start_state and end_state are set to zero.
This patch fixes the issue
This patch adds an additional argument, *uniform, to
mtrr_type_lookup(), which returns 1 when a given range is
either fully covered by a single MTRR entry or not covered
at all.
pud_set_huge() and pmd_set_huge() are changed to check the
new uniform flag to see if it is safe to create a huge page
On Tuesday 10 March 2015 16:44:24 Maxime Coquelin wrote:
> 2015-03-10 16:02 GMT+01:00 Arnd Bergmann :
> > On Friday 20 February 2015 19:01:06 Maxime Coquelin wrote:
> >> +/* AHB1 */
> >> +#define GPIOA_RESET0
> >> +#define GPIOB_RESET1
> >> +#define GPIOC_RESET2
> >> +#define
On Tuesday 10 March 2015 16:28:44 Maxime Coquelin wrote:
> 2015-03-10 16:00 GMT+01:00 Arnd Bergmann :
> > On Friday 20 February 2015 19:01:04 Maxime Coquelin wrote:
> >> Some platforms need to initialize the reset controller before the timers.
> >>
> >> This patch introduces a
On Tuesday 10 March 2015 10:10:54 Feng Kan wrote:
> +
> + soc {
> + compatible = "simple-bus";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + serial0: serial@1060 {
> +
On Tue, Mar 10, 2015 at 09:11:00PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 10, 2015 at 10:46:55PM +0530, Sudip Mukherjee wrote:
> > we were getting build warnings about assignment of incompatible
> > pointer types. some of the function definitions were having wrong
> > return type or
In 3.10.y backport patch 1dba303727f52ea062580b0a9b3f0c3b462769cf,
the logic to call pm_qos_update_target was moved to __pm_qos_update_request.
However, the original code was left in function pm_qos_update_request.
Currently, if pm_qos_update_request is called where new_value !=
req->node.prio
Now it is possible to send string and hexadecimal data as an input
parameter
v2: Fixed coding style and removed unnecessary castings from malloc
Noted by Mark Brown
modified: Documentation/spi/spidev_test.c
Signed-off-by: Adrian Remonda
---
On Tue, Mar 10, 2015 at 10:46:51PM +0530, Sudip Mukherjee wrote:
> Hi Greg,
> all the build warnings have been taken care of in this series.
> some of the patches will generate a few checkpatch warning and for some I
> tried
> to address few of the chcekpatch warnings while modifying them.
Don't
renamed:Documentation/spi/spidev_test.c -> tools/spi/spidev_test.c
Signed-off-by: Adrian Remonda
---
Documentation/spi/spidev_test.c | 318 ---
tools/spi/spidev_test.c | 318 +++
2 files changed, 318
This is the corrected version of a patch series that adds functionalities
to the spidev_test tool found in Documentation/spi/spidev_test.c.
- Cleaned hexadecimal dump
- Added verbose mode to see the transmitting sequence
- Added input buffer from the terminal. Now it is possible to send
string
v2: Fixed coding style and removed unnecessary castings
As noted by Geert Uytterhoeven and Mark Brown
modified: Documentation/spi/spidev_test.c
Signed-off-by: Adrian Remonda
---
Documentation/spi/spidev_test.c | 35 +--
1 file
Signed-off-by: Adrian Remonda
---
Documentation/spi/spidev_test.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/Documentation/spi/spidev_test.c b/Documentation/spi/spidev_test.c
index 9cb09184a3d6..4b6a3803638b 100644
--- a/Documentation/spi/spidev_test.c
+++
On Tue, Mar 10, 2015 at 10:46:55PM +0530, Sudip Mukherjee wrote:
> we were getting build warnings about assignment of incompatible
> pointer types. some of the function definitions were having wrong
> return type or arguments.
>
> Signed-off-by: Sudip Mukherjee
> ---
>
On Tue, Mar 10, 2015 at 07:59:18PM +0800, Chen-Yu Tsai wrote:
> From: Boris BREZILLON
>
> Add AXP22X regulator definitions and variant id associations.
> This introduces a new "switch" type output for one of the regulators.
> It is a switchable secondary output of one regulator, with the same
>
On Tue, Mar 10, 2015 at 12:13 PM, Denys Vlasenko wrote:
> On 03/10/2015 07:06 PM, Andy Lutomirski wrote:
>> This has confused me for a while. Now that I figured it out,
>> document it.
>
> Great!
>
>> Signed-off-by: Andy Lutomirski
>> ---
>> arch/x86/include/asm/processor.h | 21
On Tue, Mar 10, 2015 at 07:59:17PM +0800, Chen-Yu Tsai wrote:
> From: Boris BREZILLON
>
> Rework the AXP20X_ macros and probe function to support the several chip
> families, so that each family can define it's own set of regulators.
Wait, no - sorry. I'd missed the defines being added earlier
On Tue, Mar 10, 2015 at 07:59:18PM +0800, Chen-Yu Tsai wrote:
> From: Boris BREZILLON
>
> Add AXP22X regulator definitions and variant id associations.
> This introduces a new "switch" type output for one of the regulators.
> It is a switchable secondary output of one regulator, with the same
>
On Tue, Mar 10, 2015 at 07:59:17PM +0800, Chen-Yu Tsai wrote:
> From: Boris BREZILLON
>
> Rework the AXP20X_ macros and probe function to support the several chip
> families, so that each family can define it's own set of regulators.
Applied, thanks.
signature.asc
Description: Digital
On Tue, Mar 10, 2015 at 10:02:15AM +0100, Arnd Bergmann wrote:
> I actually added a bunch of these in other places, but have stopped
> doing so because Russell didn't like them, and I tend to follow
> his argument now that it's actually pretty confusing.
I'm not a big fan of my patch, but it did
On Tue, Mar 10, 2015 at 11:33:36AM -0700, Joe Perches wrote:
> On Tue, 2015-03-10 at 17:51 +0100, Arnd Bergmann wrote:
> > As the only comments I got for the "mtd: cfi: reduce stack size"
> > patch were about whitespace changes, it appears necessary to fix
> > up the rest of the file as well,
On Tue, 2015-03-10 at 01:06 +1100, Alexey Kardashevskiy wrote:
> This checks that the TCE table page size is not bigger that the size of
> a page we just pinned and going to put its physical address to the table.
>
> Otherwise the hardware gets unwanted access to physical memory between
> the end
On Mar 10, 2015, at 2:52 PM, Arnd Bergmann wrote:
> On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
>>> The top level qcom,msm-id and qcom,board-id are utilized by
>>> bootloaders
on Qualcomm MSM platforms to determine which device tree should be
Tony,
On 03/10/2015 11:09 AM, Tony Lindgren wrote:
> * Suman Anna [150309 16:59]:
>> On 03/05/2015 10:57 AM, Tony Lindgren wrote:
>>> * Suman Anna [150305 08:47]:
On 03/05/2015 09:40 AM, Tony Lindgren wrote:
> * Dave Gerlach [150304 20:14]:
Dave,
Looks like the commit
On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
> > The top level qcom,msm-id and qcom,board-id are utilized by
> > bootloaders
> >> on Qualcomm MSM platforms to determine which device tree should be
> >> utilized and passed to the kernel.
> >>
>
From: Dave Chinner
There's a small consistency problem between the inode and writeback
naming. Writeback calls the "for IO" inode queues b_io and
b_more_io, but the inode calls these the "writeback list" or
i_wb_list. This makes it hard to an new "under writeback" list to
the inode, or call it
On a box with a lot of ram (148gb) I can make the box softlockup after running
an fs_mark job that creates hundreds of millions of empty files. This is
because we never generate enough memory pressure to keep the number of inodes on
our unused list low, so when we go to unmount we have to evict
These are patches that Dave Chinner wrote two years ago that are still very much
needed today. I recently ran into a problem where I had millions of inodes that
needed to be evicted at unmount time and it soft locked up the box and kept any
other file system from doing work. These patches fix
From: Dave Chinner
When competing sync(2) calls walk the same filesystem, they need to
walk the list of inodes on the superblock to find all the inodes
that we need to wait for IO completion on. However, when multiple
wait_sb_inodes() calls do this at the same time, they contend on the
the
From: Dave Chinner
Some filesystems don't use the VFS inode hash and fake the fact they
are hashed so that all the writeback code works correctly. However,
this means the evict() path still tries to remove the inode from the
hash, meaning that the inode_hash_lock() needs to be taken
On Tue, Mar 10, 2015 at 12:22 PM, Denys Vlasenko wrote:
> On 03/10/2015 07:05 PM, Andy Lutomirski wrote:
>> x86_32, unlike x86_64, pads the top of the kernel stack. Document
>> this padding and give it a name.
>>
>> This should make no change whatsoever to the compiled kernel image.
>> It also
From: Dave Chinner
The process of reducing contention on per-superblock inode lists
starts with moving the locking to match the per-superblock inode
list. This takes the global lock out of the picture and reduces the
contention problems to within a single filesystem. This doesn't get
rid of
From: Dave Chinner
Doing writeback on lots of little files causes terrible IOPS storms
because of the per-mapping writeback plugging we do. This
essentially causes imeediate dispatch of IO for each mapping,
regardless of the context in which writeback is occurring.
IOWs, running a concurrent
From: Dave Chinner
The per-superblock inode list and lock is a bottleneck for systems
that cycle inodes in and out of cache concurrently. The global lock
is a limiting factor.
Most of the additions to the sb inode list occur on the CPU that
allocated the inode, and most of the removals occur
From: Dave Chinner
wait_sb_inodes() current does a walk of all inodes in the filesystem
to find dirty one to wait on during sync. This is highly
inefficient and wastes a lot of CPU when there are lots of clean
cached inodes that we don't need to wait on.
To avoid this "all inode" walk, we need
201 - 300 of 1866 matches
Mail list logo
