3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e70ab977991964a5a7ad1182799451d067e62669 upstream.
While PROC_CN_MCAST_LISTEN/IGNORE is entirely advisory, it was possible
for an unprivileged user to turn off notifications
From: Jan-Simon Möller
Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
compliant equivalent. This is the original VLAIS struct.
struct {
struct aead_request req;
u8 priv[crypto_aead_reqsize(tfm)];
} aead_req;
This patch instead
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Edwards
commit 27ef63c7e97d1e585051c03f8d44cc887f34 upstream.
When determining the page size we could use to map with the IOMMU, the
page size should also be aligned with the hva, not
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dominik Dingel
commit 2b29a9fdcb92bfc6b6f4c412d71505869de61a56 upstream.
Any uaccess between guest_enter and guest_exit could trigger a page fault,
the page fault handler would handle it as a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jiang Liu
commit 08dff7b7d629807dbb1f398c68dd9cd58dd657a1 upstream.
When online_pages() is called to add new memory to an empty zone, it
rebuilds all zone lists by calling
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 14611e51a57df10240817d8ada510842faf0ec51 upstream.
task->cgroups is a RCU pointer pointing to struct css_set. A task
switches to a different css_set on cgroup migration but a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 5edee61edeaaebafe584f8fb7074c1ef4658596b upstream.
cgroup core has a bug which violates a basic rule about event
notifications - when a new entity needs to be added, you add
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vyacheslav Dubeyko
commit 7f42ec3941560f0902fe3671e36f2c20ffd3af0a upstream.
Many NILFS2 users were reported about strange file system corruption
(for example):
NILFS: bad btree node
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnaldo Carvalho de Melo
commit 42e1fb776087713b5482cd7cf6cac998fbdd6544 upstream.
Noticed while developing a 'perf test' entry to verify that
perf_evsel__name works.
Cc: David Ahern
Cc:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Miklos Szeredi
commit efeb9e60d48f7778fdcad4a0f3ad9ea9b19e5dfd upstream.
Userspace can add names containing a slash character to the directory
listing. Don't allow this as it could cause all
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit bd8ba20597f0cfef3ef65c3fd2aa92ab23d4c8e1 upstream.
Some devices have duplicate entries in there brightness levels table, ie
on my Dell Latitude E6430 the table looks like
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lan Tianyu
commit f3ca4164529b875374c410193bbbac0ee960895f upstream.
acpi_processor_set_throttling() uses set_cpus_allowed_ptr() to make
sure that the (struct
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksander Morgado
commit 12df84d4a80278a5b1abfec3206795291da52fc9 upstream.
This interface is to be handled by the qmi_wwan driver.
CC: Hans-Christoph Schemmel
CC: Christian Schmiedl
CC:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit 73d9f7eef3d98c3920e144797cc1894c6b005a1e upstream.
For nofail == false request, if __map_request failed, the caller does
cleanup work, like releasing the relative pages. It
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Olsa
commit 275ef3878f698941353780440fec6926107a320b upstream.
If the event name is specified with all 3 components, the last one
overwrites the previous one during the name composing
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit 860d21e2c585f7ee8a4ecc06f474fdc33c9474f4 upstream.
The only reason for sb_getblk() failing is if it can't allocate the
buffer_head. So ENOMEM is more appropriate than
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lai Jiangshan
commit 5bdfff96c69a4d5ab9c49e60abf9e070ecd2acbb upstream.
When a kworker should die, the kworkre is notified through WORKER_DIE
flag instead of kthread_should_stop(). This,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 9f9c47f00ce99329b1a82e2ac4f70f0fe3db549c upstream.
It's a bit odd to see a newer device showing mod15write; however, the
reported behavior is highly consistent and other
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit bd49940a35ec7d488ae63bd625639893b3385b97 upstream.
As the initial domain we are able to search/map certain regions
of memory to harvest configuration data. For all
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit 888b65b4bc5e7fcbbb967023300cd5d44dba1950 upstream.
In the PVHVM path when we do CPU online/offline path we would
leak the timer%d IRQ line everytime we do a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit e6355ad7b1c6f70e2f48ae159f5658b441ccff95 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
[wml: Backported to 3.4:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 500a91571f0a5d0d3242d83802ea2fd1faccc66e upstream.
When trying to set the minimum temperature, the driver was erroneously
writing the maximum temperature into the chip.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 8d9256906a97c24e97e016482b9be06ea2532b05 upstream.
Backends may need to protect themselves against an insane number of
produced requests stored by a frontend, in case they
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 757c4f6260febff982276818bb946df89c1105aa upstream.
David reported that commit c2b93e06 (cifs: only set ops for inodes in
I_NEW state) caused a regression with mfsymlinks.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Liu
commit 2810e5b9a7731ca5fce22bfbe12c96e16ac44b6f upstream.
This patch tries to coalesce tx requests when constructing grant copy
structures. It enables netback to deal with situation
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit 9371cadbbcc7c00c81753b9727b19fb3bc74d458 upstream.
commit 8e3f8755545cc4a7f4da8e9ef76d6d32e0dca576 upstream.
Check that the ring does not have an insane amount of
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Vrabel
commit 5e72fdb8d827560893642e85a251d339109a00f4 upstream.
commit 4704fe4f03a5ab27e3c36184af85d5000e0f8a48 upstream.
When a event is being bound to a VCPU there is a window
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 506026c3ec270e18402f0c9d33fee37482c23861 upstream.
rpc_make_runnable is not generally called with the queue lock held, unless
it's waking up a task that has been sitting on
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit a3c3cac5d31879cd9ae2de7874dc6544ca704aec upstream.
The lockless RPC_IS_QUEUED() test in __rpc_execute means that we need to
be careful about ordering the calls to
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sascha Hauer
commit b6e51600f4e983e757b1b6942becaa1ae7d82e67 upstream.
Signed-off-by: Sascha Hauer
Signed-off-by: Markus Pargmann
Signed-off-by: Mark Brown
[bwh: Backported to 3.2: adjust
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Dorchain
commit 6dbd46c849e071e6afc1e0cad489b0175bca9318 upstream.
Hello,
the following patch adds an entry for the PID of a Cressi Leonardo
diving computer interface to kernel 3.13.0.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 5b9ab3f7324a1b94a5a5a76d44cf92dfeb3b5e80 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
Signed-off-by: Ben
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit 66ff0fe9e7bda8aec99985b24daad03652f7304e upstream.
While we don't use the spinlock interrupt line (see for details
commit f10cd522c5fbfec9ae3cc01967868c9c2401ed23
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit cc7282b8d5abbd48c81d1465925d464d9e3eaa8f upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
Signed-off-by: Ben
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Fabio Estevam
commit 016fcab8ff46fca29375d484226ec91932aa4a07 upstream.
According to the sgtl5000 reference manual, the default value of CHIP_SSS_CTRL
is 0x10.
Reported-by: Oskar Schirmer
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 9538aa46c2427d6782aa10036c4da4c541605e0e upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Acked-by: Clemens Ladisch
Signed-off-by: Takashi Iwai
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 5be1efb4c2ed79c3d7c0cbcbecae768377666e84 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
Signed-off-by: Ben
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: stephen hemminger
commit 9eaee8beeeb3bca0d9b14324fd9d467d48db784c upstream.
Fix warning about 0 used as NULL.
Signed-off-by: Stephen Hemminger
Signed-off-by: David S. Miller
Signed-off-by:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Chiluk
commit 698b8223631472bf982ed570b0812faa61955683 upstream.
1d2ef5901483004d74947bbf78d5146c24038fe7 caused a regression in ncpfs such that
directories could no longer be removed.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Liu
commit 03393fd5cc2b6cdeec32b704ecba64dbb0feae3c upstream.
Some frontend drivers are sending packets > 64 KiB in length. This length
overflows the length field in the first slot making
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Thomas
commit 8afd500cb52a5d00bab4525dd5a560d199f979b9 upstream.
The last orphan in the dnext list has its dnext set to NULL. Because
of that, ubifs_delete_orphan assumes that it is not
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit d76a3a77113db020d9bb1e894822869410450bd9 upstream.
In the case where an inode has a very stale transaction id (tid) in
i_datasync_tid or i_sync_tid, it's possible that
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 61be2b9a18ec70f3cbe3deef7a5f77869c71b5ae upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Acked-by: Mark Brown
Signed-off-by: Takashi Iwai
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Roland Dreier
commit 893d290f1d7496db97c9471bc352ad4a11dc8a25 upstream.
After we've done __elv_add_request() and __blk_run_queue() in
blk_execute_rq_nowait(), the request might finish and be
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
commit 08a5dd3842f2ac61c6d69661d2d96022df8ae359 upstream.
Add some new PCI IDs to the table for 6000, 6005 and 6235 series.
Signed-off-by: Emmanuel Grumbach
Signed-off-by:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Maxim Patlasov
commit 06a7c3c2781409af95000c60a5df743fd4e2f8b4 upstream.
The way how fuse calls truncate_pagecache() from fuse_change_attributes()
is completely wrong. Because, w/o i_mutex
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 9186a1fd9ed190739423db84bc344d258ef3e3d7 upstream.
If channel switch is pending and we remove interface we can
crash like showed below due to passing NULL vif to
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lucas Stach
commit 8b5b6f5413e97c3e8bafcdd67553d508f4f698cd upstream.
ASIX AX88772B started to pack data even more tightly. Packets and the ASIX
packet
header may now cross URB boundaries. To
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Cave-Ayland
commit 0c5d63f0ab6728f05ddefa25aff55e31297f95e6 upstream.
All of the rtlwifi drivers have an error in the routine that tests if
the data is "special". If it is, the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 091e26dfc156aeb3b73bc5c5f277e433ad39331c upstream.
Running AIO is pinning inode in memory using file reference. Once AIO
is completed using aio_complete(), file reference is
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 86f0b5b86d142b9323432fef078a6cf0fb5dda74 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
Signed-off-by: Ben
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 60478295d6876619f8f47f6d1a5c25eaade69ee3 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Signed-off-by: Takashi Iwai
Cc: Weng Meiling
2014-03-07 3:34 GMT-08:00 Sebastian Hesselbarth
:
> commit 1211ce53077164e0d34641d0ca5fb4d4a7574498
> ("net: phy: resume/suspend PHYs on attach/detach")
> introduced a feature to suspend PHYs when entering halted state.
>
> Unfortunately, not all bootloaders properly power-up PHYs on reset
> and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 707aee401d2467baa785a697f40a6e2d9ee79ad5 upstream.
The BT_CONFIG command that is sent to the device during
startup will enable BT coex unless the module parameter
turns
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 94543a8d4fb302817014981489f15cb3b92ec3c2 upstream.
iwl_dbgfs_fh_reg_read() can cause crashes and/or
BUG_ON in slub because the ifdefs are wrong, the
code in iwl_dump_fh()
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 4fc79db178f0a0ede479b4713e00df2d106028b3 upstream.
If the device is not started, we can't read its
SRAM and attempting to do so will cause issues.
Protect the debugfs
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 7c34158231b2eda8dcbd297be2bb1559e69cb433 upstream.
The RX replenish code doesn't handle DMA mapping failures,
which will cause issues if there actually is a failure. This
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Clements
commit c378f70adbc1bbecd9e6db145019f14b2f688c7c upstream.
Currently, when a disconnect is requested by the user (via NBD_DISCONNECT
ioctl) the return from NBD_DO_IT is undefined
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 46f6c1aaf790be9ea3c8ddfc8f235a5f677d08e2 upstream.
snd_pcm_stop() must be called in the PCM substream lock context.
Acked-by: Mark Brown
Signed-off-by: Takashi Iwai
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 8a964f44e01ad3bbc208c3e80d931ba91b9ea786 upstream.
The FH hardware will always write back to the scratch field
in commands, even host commands not just TX commands, which
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
commit 25a172655f837bdb032e451f95441bb4acec51bb upstream.
This can lead to a panic if the driver isn't ready to
handle them. Since our interrupt line is shared, we can get
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nithin Sujir
[ Upstream commit c6993dfd7db9b0c6b7ca7503a56fda9236a4710f ]
Quoting David Vrabel -
"5780 cards cannot have jumbo frames and TSO enabled together. When
jumbo frames are enabled
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 31efee60f489c759c341454d755a9fd13de8c03d upstream.
When a call goes out, the signing code adjusts the sequence number
upward by two to account for the request and the
On Fri, Mar 07, 2014 at 06:30:45PM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> Here's my pull request for v3.15 merge window.
>
> This pull request contains patches which have been soaking in linux-next for
> quite a bit of time. I also ran everything through my 150 randconfigs script
> (which
[+cc Rafael]
On Fri, Mar 07, 2014 at 11:39:48AM -0800, Yinghai Lu wrote:
> On Fri, Mar 7, 2014 at 8:45 AM, Bjorn Helgaas wrote:
> >
> > I opened a bugzilla report at
> > https://bugzilla.kernel.org/show_bug.cgi?id=71691
> >
> > It seems like clearing DisINTx has some effect on MSI. I don't see
This forces the entire per_cpu range to be reported as absolute
without losing their linker symbol types, when the per_cpu area is
0-based. Without this, the variables are incorrectly shown as relocated
under kASLR on x86_64.
Several kallsyms output in different boot states for comparison of
Handles 0-based per_cpu variables as being absolute so they are
not relocated under kASLR on x86_64.
-Kees
--
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
This refactors the address range checks to be generalized instead of
specific to text range checks, in preparation for other range checks.
Also extracts logic for "is the symbol absolute" into a function.
Signed-off-by: Kees Cook
---
v2:
- return which range entry index an address was found in.
On Friday, March 07, 2014 5:42 PM, Chase Southwood wrote:
>
> This patch fixes the register map defines for the digital input registers
> such that they are all the real offsets to each register, rather than a
> mix of real offsets and adders to those offsets.
>
> Further, some of the old defines
On 03/07/14 14:56, PaX Team wrote:
On 7 Mar 2014 at 11:08, beh...@converseincode.com wrote:
diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
index c3eb102..5ce1f67 100644
--- a/include/linux/moduleparam.h
+++ b/include/linux/moduleparam.h
@@ -346,6 +346,7 @@ static inline
From: Eric Paris
Date: Fri, 07 Mar 2014 17:52:02 -0500
> Audit is non-tolerant to failure and loss.
Netlink is not a loss-less transport.
--
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
On Sat, 08 Mar 2014 09:12:31 +0900
Satoru Takeuchi wrote:
> Hi Steven,
>
> At Sun, 02 Mar 2014 21:20:31 +0900,
> Satoru Takeuchi wrote:
> >
> > From: Satoru Takeuchi
> >
> > If we'd like to set the redirect target file of run_command(),
> > we should define $redirect before calling this
This patch fixes the register map defines for the counter registers such
that they are all the real offsets to each register, rather than a mix of
real offsets and adders to those offsets.
Signed-off-by: Chase Southwood
---
2: Simplified commit message, fixed indentation and whitespace damage.
This patch for fixes the register map defines for the watchdog registers
such that they are all the real offsets to each register, rather than a
mix of real offsets and adders to those offsets.
Signed-off-by: Chase Southwood
---
2: Simplified commit message, fixed indentation and whitespace
This patch for fixes the register map defines for the timer registers such
that they are all the real offsets to each register, rather than a mix of
real offsets and adders to those offsets.
Signed-off-by: Chase Southwood
---
2: Simplified commit message, fixed indentation and whitespace
This patch fixes the register map defines for the digital output registers
such that they are all the real offsets to each register, rather than a
mix of real offsets and adders to those offsets.
Further, some of the old defines were being used incorrectly in the
i_APCI1564_Reset() function.
This patch fixes the register map defines for the digital input registers
such that they are all the real offsets to each register, rather than a
mix of real offsets and adders to those offsets.
Further, some of the old defines were being used incorrectly in the
i_APCI1564_Reset() function. Upon
>On Friday, March 7, 2014 11:38 AM, Hartley Sweeten
> wrote:
>>On Friday, March 07, 2014 1:38 AM, Chase Southwood wrote:
>>This patch fixes the register map defines for the counter registers such
>>that they are all the real offsets to each register, rather than a mix of
>>real offsets and
Hi Greg,
Here's my pull request for v3.15 merge window.
This pull request contains patches which have been soaking in linux-next for
quite a bit of time. I also ran everything through my 150 randconfigs script
(which uses some seeds of my own).
Please, consider merging it on top of your
Looks like this is unintentional as the
result = EEH_STATE_UNAVAILABLE is being
overwritten by EEH_STATE_NOT_SUPPORT in the
fallthrough to the default case.
---
diff --git a/arch/powerpc/platforms/pseries/eeh_pseries.c
b/arch/powerpc/platforms/pseries/eeh_pseries.c
index 8a8f047..83da53f 100644
On Fri, 2014-03-07 at 09:15 -0800, Dave Hansen wrote:
> On 03/06/2014 05:55 PM, Davidlohr Bueso wrote:
> > On Wed, 2014-03-05 at 16:45 -0800, Dave Hansen wrote:
> >> From: Dave Hansen
> >>
> >> Now that we have some shiny new tracepoints, we can actually
> >> figure out what the heck is going on.
On Fri, Mar 7, 2014 at 1:25 PM, Andrew Morton wrote:
> On Fri, 7 Mar 2014 10:58:43 +0800 Liu ShuoX wrote:
>
>>
>> ftrace_read_cnt need to be reset in open to support mutli times
>> getting the records.
>>
>> Signed-off-by: Liu ShuoX
>> ---
>> fs/pstore/ram.c | 3 ++-
>> 1 file changed, 2
Hi Steven,
At Sun, 02 Mar 2014 21:20:31 +0900,
Satoru Takeuchi wrote:
>
> From: Satoru Takeuchi
>
> If we'd like to set the redirect target file of run_command(),
> we should define $redirect before calling this function and should undef it
> after calling this function. Since it's
On Fri, 2014-03-07 at 11:13AM -0800, Soren Brinkmann wrote:
> Use 'CDNS_UART' or 'cdns_uart' instead of 'XUARTPS' and 'xuartps' as
> function and symbol prefix. This is essentially doing:
> - s/XUARTPS/CDNS_UART/g
> - s/xuartps/cdns_uart/g
> The only exception is PORT_XUARTPS, which stays as is,
On 7 Mar 2014 at 11:08, beh...@converseincode.com wrote:
> diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
> index c3eb102..5ce1f67 100644
> --- a/include/linux/moduleparam.h
> +++ b/include/linux/moduleparam.h
> @@ -346,6 +346,7 @@ static inline void destroy_params(const
Hi Stefani,
> So i tried my best, but without support it is impossible to find all
> issues. But mostly what i get was bureaucracy afflictions
>
> I complied, but now it is time to help finding the issues. And not only
> do a complain, sit back and wait.
I feel sorry if that's what you
The current vendor compatible check will not match vendors with
dashes, like:
compatible="asahi-kasei"
Reported-by: Joe Perches
Signed-off-by: Florian Vaussard
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl
With a compatible string like
compatible = "foo";
checkpatch will currently try to find "foo" in vendor-prefixes.txt,
which is wrong since the vendor prefix is empty in this specific case.
Skip the vendor test if the compatible is not like
compatible = "vendor,something";
Signed-off-by:
Hi,
This series proposes a number of fixes and enhancements to the checks
performed on compatible strings:
1) Fix vendor check for strings with dashes
2) Fix spurious vendor warning, when there is no vendor
3) Check for compatible strings in .c and .h files too
4) Match only at the begining of
Improve the vendor name match in vendor-prefix.txt
by only matching the exact vendor name at the beginning of lines.
Signed-off-by: Florian Vaussard
---
scripts/checkpatch.pl | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/scripts/checkpatch.pl
Look for ".compatible = "foo" strings not only in .dts files, but
in .c and .h too.
Signed-off-by: Florian Vaussard
---
scripts/checkpatch.pl | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 96f10ba..9205153 100755
---
Hi Linus,
A small collection of minor fixes. The FPU stuff is still pending, I
fear. I haven't heard anything from Suresh so I suspect I'm going to
have to dig into the init specifics myself and fix up the patchset.
The following changes since commit 0414855fdc4a40da05221fc6062cccbc0c30f169:
Placeholders <..> are sometimes used in the devicetree documentation
to define family-wide compatible strings (like fsl,-ipu where
chip can be any Freescale SoC).
These placeholders are loosly defined. This lead to some
fragmentation. Looking at the current placeholders, we have:
3
Hi Suresh,
Any thoughts on this?
-hpa
On 02/27/2014 03:44 PM, H. Peter Anvin wrote:
> So, picking up this thread which got dropped on the floor...
>
> On 02/01/2014 11:19 PM, Suresh Siddha wrote:
>>
>> diff --git a/arch/x86/kernel/i387.c b/arch/x86/kernel/i387.c
>> index
On Fri, 2014-03-07 at 11:13AM -0800, Soren Brinkmann wrote:
> The Xilinx UARTPS driver has been renamed to Cadence UART. Remove
> the stale Xilinx UARTPS config options and add Cadence UART instead.
This will also be dropped, since the corresponding renaming of config
symbol gets dropped.
On Sat, 2014-03-08 at 02:04 +0300, Dan Carpenter wrote:
> On Fri, Mar 07, 2014 at 01:30:17PM -0800, j...@joshtriplett.org wrote:
> > On Fri, Mar 07, 2014 at 01:02:44PM -0800, Joe Perches wrote:
> > > On Fri, 2014-03-07 at 15:41 -0500, David Miller wrote:
> > > > From: Alistair Popple
> > > >
Commit-ID: 5fa10196bdb5f190f595ebd048490ee52dddea0f
Gitweb: http://git.kernel.org/tip/5fa10196bdb5f190f595ebd048490ee52dddea0f
Author: H. Peter Anvin
AuthorDate: Fri, 7 Mar 2014 15:05:20 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 7 Mar 2014 15:08:14 -0800
x86: Ignore NMIs that
On 03/07/2014 08:06 AM, Stefani Seibold wrote:
>>
>> wfg@bee /tmp% git clone --reference /c/linux
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>
> As i wrote i already cloned the tip tree!!
>
> But i cannot see the changeset, there is also no VDSO changes set in the
> git
Hi
On Fri, Mar 7, 2014 at 10:58 PM, One Thousand Gnomes
wrote:
>> - The renderer supports *any* RGB target, from 8bit to 32bit with
>>big-endian and little-endian support. The related pixel-renderer will
>>probably never win a beauty-contest, but it works.. Again, who cares
>>for
On Mon, Mar 03, 2014 at 09:38:03AM +, Shevchenko, Andriy wrote:
> > + if (IS_ERR(bdev->bamclk))
> > + return PTR_ERR(bdev->bamclk);
> > +
> > + ret = clk_prepare_enable(bdev->bamclk);
> > + if (ret) {
> > + dev_err(bdev->dev, "failed to prepare/enable clock\n");
>
101 - 200 of 1502 matches
Mail list logo
