On Tue 2015-09-29 14:29:19, Tomeu Vizoso wrote:
> If a suitable prepare callback cannot be found for a given device and
> its driver has no PM callbacks at all, assume that it can go direct to
> complete when the system goes to sleep.
>
> The reason for this is that there's lots of devices in a sy
On Sun, 4 Oct 2015, Peter Senna Tschudin wrote:
> On Fri, Oct 2, 2015 at 7:52 PM, Alan Stern wrote:
> > On Fri, 2 Oct 2015, Felipe Balbi wrote:
> >
> >> On Mon, Sep 21, 2015 at 05:01:10PM +0200, Peter Senna Tschudin wrote:
> >> > msleep under 20ms can result in sleeping up to 20ms, which may not
On Sun, 4 Oct 2015, Eric Curtin wrote:
> Ok so for the fun of it, I changed the VENDOR_ID and DEVICE_ID of my
> keyboard to use the driver for this samsung Wireless keyboard and
> mouse, crazy I know since I have a different piece of hardware, but I
> wanted to see what happens or at least does it
The IO configuration was not used to configure the board. It was only
read from the configuration file. Stop reading it and also remove the
other related variables defined for it.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/dgap/dgap.c | 21 -
drivers/staging/dgap/dga
On Thu, Sep 10, 2015 at 8:43 PM, Chris Metcalf wrote:
>
> Please pull the following changes for 4.3 from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git
> strscpy
So I finally pulled it. I like the patch, I like the new interface,
but despite that I wasn't really sur
This driver code was found as:
https://android.googlesource.com/kernel/tegra/+/aaabb2e045f31e5a970109ffdaae900dd403d17e/drivers/staging/iio/adc
Fixed various compilation issues and test this driver on omap5 evm.
Signed-off-by: Pradeep Goudagunta
Signed-off-by: H. Nikolaus Schaller
Signed-off-b
Your subject is really "odd", it doesn't really describe what you are
doing in a single line, it just has a file name in it :(
What did you use to generate these? I got a few duplicates, and there
isn't a "leading" 0 for the first 9 patches. git can spit these out
correctly very simply, I recomm
Hi,
Resending this patch series as requested by Greg. So he can have them in his
queue for picking up.
https://lkml.org/lkml/2015/10/4/76
These patches add the missing MODULE_DEVICE_TABLE() for OF to export
the information so modules have the correct aliases built-in and
autoloading works correct
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
Acked-by: Scott Wood
---
drivers/memory/fsl-corenet-cf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/memory/fsl-c
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
drivers/memory/ti-aemif.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/memory/ti-aemif.c b/drivers/memory/ti-ae
On 08/04/2015 02:29 PM, Toralf Förster wrote:
> On 08/02/2015 09:43 AM, Pavel Machek wrote:
>> Any chance to bisect it?
> Did it.
>
> FWIW: the mentioned commit was introduced between 3.18 and 3.19.
> But my system (hardened 64 bit Gentoo) did not suffer from it till version
> 4.0.8.
> The harden
You all know the drill by now. It's Sunday, and there is a new release
candidate out there.
Things look fairly normal. We have noticeably fewer commits than rc3
(which was fairly big), and I don't see anything unusually alarming.
The statistics look pretty normal too: just under half of the patch
On Sat, Oct 03, 2015 at 08:13:36PM +0200, Oleg Nesterov wrote:
> 1. Rename dequeue_signal_lock() to kernel_dequeue_signal(). This
>matches another "for kthreads only" kernel_sigaction() helper.
>
> 2. Remove the "tsk" and "mask" arguments, they are always current
>and current->blocked. And
Change the chapters related to uio_pci_generic that refer interrupt mode.
Add the relevant explanation regarding MSI and MSI-X interrupt modes
support.
Signed-off-by: Vlad Zolotarov
---
Documentation/DocBook/uio-howto.tmpl | 29 ++---
1 file changed, 26 insertions(+), 3 d
This series add support for MSI and MSI-X interrupts to uio_pci_generic driver.
Currently uio_pci_generic supports only legacy INT#x interrupts source. However
there are situations when this is not enough, for instance SR-IOV VF devices
that
simply don't have INT#x capability. For such devices ui
Signed-off-by: Vlad Zolotarov
---
drivers/uio/uio.c | 15 +++
include/linux/uio_driver.h | 3 +++
2 files changed, 18 insertions(+)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 8196581..714b0e5 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -704,6 +70
Add support for MSI and MSI-X interrupt modes:
- Interrupt mode selection order is:
INT#X (for backward compatibility) -> MSI-X -> MSI.
- Add ioctl() commands:
- UIO_PCI_GENERIC_INT_MODE_GET: query the current interrupt mode.
- UIO_PCI_GENERIC_IRQ_NUM_GET: query the maximu
FYI: I've just posted to linux-kernel list patches that add support for
both MSI and MSI-X interrupt modes to uio_pci_generic driver.
It addresses most (all) remarks on this thread and also fixes some
issues this code has, e.g. not disabling msi-x in remove(), etc.
U are all welcome to comment.
Hi Xing,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: arm-arm67 (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
Hi Vlad,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
config: xtensa-allyesconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/
The xattr_handler operations are currently all passed a file system
specific flags value which the operations can use to disambiguate between
different handlers; some file systems use that to distinguish the xattr
namespace, for example. In some oprations, it would be useful to also have
access to
This is version three of the xattr cleanups. The main change in the series
is to pass struct xattr_handler down to the xattr handler operations. In
addition, a few other small problems in the code are fixed.
What's missing is a fix for ocfs2's listxattr operation: ocfs2 implements
list xattr han
Ubifs installs a security xattr handler in sb->s_xattr but doesn't use the
generic_{get,set,list,remove}xattr inode operations needed for processing
this list of attribute handlers; the handler is never called. Instead,
ubifs uses its own xattr handlers which also process security xattrs.
Remove
The list operations can never be called; they are even documented to be
unused.
Signed-off-by: Andreas Gruenbacher
Reviewed-by: Christoph Hellwig
---
fs/hfsplus/xattr.c | 11 ---
fs/hfsplus/xattr_security.c | 11 ---
fs/hfsplus/xattr_trusted.c | 11 ---
fs/hfsp
Now that the xattr handler is passed to the xattr handler operations, we
have access to the attribute name prefix, so simplify
f2fs_xattr_generic_list.
Also, f2fs_xattr_advise_list is only ever called for
f2fs_xattr_advise_handler; there is no need to double check for that.
Signed-off-by: Andreas
Now that the xattr handler is passed to the xattr handler operations, we
have access to the attribute name prefix, so simplify the squashfs xattr
handlers a bit.
Signed-off-by: Andreas Gruenbacher
Cc: Phillip Lougher
---
fs/squashfs/xattr.c | 90 ++---
The vfs checks if a task has the appropriate access for get and set
operations, but it cannot do that for the list operation; the file system
must check for that itself.
Signed-off-by: Andreas Gruenbacher
Reviewed-by: Christoph Hellwig
Cc: David Woodhouse
Cc: linux-...@lists.infradead.org
---
Now that the xattr handler is passed to the xattr handler operations, we
can use the same get and set operations for the user, trusted, and security
xattr namespaces. In those namespaces, we can access the full attribute
name by "reattaching" the name prefix the vfs has skipped for us. Add a
xatt
Hello Chen,
On Sun, Oct 04, 2015 at 12:55:29PM +0800, Chen Gang wrote:
> Theoretically, the lock and unlock need to be symmetric, if we have to
> lock f_mapping all firstly, then lock all anon_vma, probably, we also
> need to unlock anon_vma all, then unlock all f_mapping.
They don't need to be s
On Sat, Oct 03, 2015 at 08:13:38PM +0200, Oleg Nesterov wrote:
> jffs2_garbage_collect_thread() can race with SIGCONT and sleep in
> TASK_STOPPED state after it was already sent. Add the new helper,
> kernel_signal_stop(), which does this correctly.
>
> Signed-off-by: Oleg Nesterov
Reviewed-by:
On Sat, Oct 03, 2015 at 08:13:41PM +0200, Oleg Nesterov wrote:
> jffs2_garbage_collect_thread() does allow_signal(SIGCONT) for no reason,
> SIGCONT will wake a stopped task up even if it is ignored.
>
> Signed-off-by: Oleg Nesterov
Reviewed-by: Tejun Heo
Thanks.
--
tejun
--
To unsubscribe fr
Signed-off-by: Vlad Zolotarov
---
drivers/uio/uio.c | 15 +++
include/linux/uio_driver.h | 3 +++
2 files changed, 18 insertions(+)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 8196581..714b0e5 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -704,6 +70
Change the chapters related to uio_pci_generic that refer interrupt mode.
Add the relevant explanation regarding MSI and MSI-X interrupt modes
support.
Signed-off-by: Vlad Zolotarov
---
Documentation/DocBook/uio-howto.tmpl | 29 ++---
1 file changed, 26 insertions(+), 3 d
This series add support for MSI and MSI-X interrupts to uio_pci_generic driver.
Currently uio_pci_generic supports only legacy INT#x interrupts source. However
there are situations when this is not enough, for instance SR-IOV VF devices
that
simply don't have INT#x capability. For such devices u
Add support for MSI and MSI-X interrupt modes:
- Interrupt mode selection order is:
INT#X (for backward compatibility) -> MSI-X -> MSI.
- Add ioctl() commands:
- UIO_PCI_GENERIC_INT_MODE_GET: query the current interrupt mode.
- UIO_PCI_GENERIC_IRQ_NUM_GET: query the maximu
The elections for five of the ten members of the Linux Foundation
Technical Advisory Board[TAB] are held every year[1]. This year the
election will be at the 2015 Kernel Summit in Seoul, South Korea
(probably on the Monday, 26 October) and will be open to all attendees
of both Kernel Summit and Kor
On Tue, Aug 25, 2015 at 11:57:09AM +0300, Noam Camus wrote:
> From: Noam Camus
>
> Add support for UPIO_MEM32BE in addition to UPIO_MEM32.
> dw8250_serial_out32() extra functionality that is not part of
> the 8250 core driver was moved to new function called
> dw8250_check_LCR().
>
> For big end
Rainer Weikusat writes:
> Mathias Krause writes:
>> On 2 October 2015 at 22:43, Jason Baron wrote:
>>> The unix_dgram_poll() routine calls sock_poll_wait() not only for the wait
>>> queue associated with the socket s that we are poll'ing against, but also
>>> calls
>
> [useless full-quote remo
Hi Vlad,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please
ignore]
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/uio/uio_pci_generic.c:93:3
On Sun, Oct 4, 2015 at 7:10 PM, 'Kostya Serebryany' via kasan-dev
wrote:
>
>
> On Sun, Oct 4, 2015 at 5:14 AM, Dmitry Vyukov wrote:
>>
>> On Sat, Oct 3, 2015 at 1:31 PM, Andrey Ryabinin
>> wrote:
>> > 2015-10-03 13:54 GMT+03:00 Thomas Gleixner :
>> >> On Fri, 2 Oct 2015, Sasha Levin wrote:
>> >>
On Tue, Sep 22, 2015 at 11:46:27PM +0200, Guillaume Gomez wrote:
> Signed-off-by: Guillaume Gomez
> ---
> drivers/tty/tty_ldisc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
> index 71750cb..5af8f18 100644
> --- a/dri
Fix using the bare numbers to set the 'bDescriptorType' descriptor fields
while the values are #define'd in .
Signed-off-by: Sergei Shtylyov
---
The patch is against the 'usb-next' branch of Greg KH's 'usb.git' repo.
I's been laying around from the end of March. :-(
drivers/usb/core/hcd.c
On Mon, Sep 21, 2015 at 10:38:20AM -0300, Emilio López wrote:
> According to the sysfs header file:
>
> "The returned value will replace static permissions defined in
> struct attribute or struct bin_attribute."
>
> but this isn't the case, as is_visible is only called on struct attribut
Hi Jarkko,
thanks for the clearification...
However, I'd recommend against doing so.
Furthermore, if there is a resource-manager running in userspace, applications
only get virtual handles and TPM might be empty actually...
If that's what you're aiming for, I'd recommend passing the pointer to
On Saturday 03 October 2015 01:53:46 Luis R. Rodriguez wrote:
> >
> > Hmm, my gut feeling tells me that your approach won't solve the problem
> > in general. s390 PCI is just weird in many ways and it will occasionally
> > suffer from problems like this (as do other aspects of the s390 architectur
On Sun, Oct 04, 2015 at 07:49:35PM +0300, Vlad Zolotarov wrote:
> FYI: I've just posted to linux-kernel list patches that add support for both
> MSI and MSI-X interrupt modes to uio_pci_generic driver.
> It addresses most (all) remarks on this thread and also fixes some issues
> this code has, e.g.
On Sunday 04 October 2015 01:22:50 Gabriel Laskar wrote:
> The i2o subsystem was removed by
> commit 4a72a7af462d ("staging: remove i2o subsystem") but the header was
> still used by drivers/scsi/dpt_i2o.c driver.
>
> This patch moves the structures used from the header into dpti_i2o.h.
>
> CC: A
On Fri, Sep 25, 2015 at 08:22:25PM +0200, Rasmus Villemoes wrote:
> The only user of the lvalue-ness of the cpu_*_mask variables is in
> drivers/base/cpu.c, and that is mostly a work-around for the fact that
> not even const variables can be used in static initialization. Now
> that the underlying
On Sun, Aug 09, 2015 at 05:01:16PM -0500, Eric Biggers wrote:
> Update the help text to account for the fact that the kernel can now load
> firmware directly from the filesystem. Also clarify how the FW_LOADER
> option works.
>
> Signed-off-by: Eric Biggers
> ---
> drivers/base/Kconfig | 33 +++
On Tue, Aug 04, 2015 at 03:00:01PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> Historically firmware_class code was added to help
> get device driver firmware binaries but these days
> request_firmware*() helpers are being repurposed for
> general system data needed by the ker
Since the first attempt at making selinux work on top of gfs2 and similar file
systems [1] was met with resistance by Christoph, here is another attempt that
doesn't require any additional inode operations, but also doesn't guarantee
full consistency of inode security labels: in case we cannot relo
When gfs2 releases the glock of an inode, it must invalidate all
information cached for that inode, including the page cache and acls. Use
the new security_inode_invalidate_secctx hook to also invalidate security
labels in that case. These items will be reread from disk when needed
after reacquir
Signed-off-by: Guillaume Gomez
---
drivers/tty/tty_ldisc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
index 71750cb..5af8f18 100644
--- a/drivers/tty/tty_ldisc.c
+++ b/drivers/tty/tty_ldisc.c
@@ -319,7 +319,7 @@ __tty_ldis
Add a hook to invalidate an inode's security label when the cached
information becomes invalid.
Implement the new hook in selinux: set a flag when a security label becomes
invalid. When hitting a security label which has been marked as invalid in
inode_has_perm, try reloading the label.
If an in
On Wed, Sep 16, 2015 at 07:09:08PM +0300, Pantelis Antoniou wrote:
> We are going to need the overlays to appear on sysfs with runtime
> global properties (like master enable) so turn them into kobjects.
>
> Signed-off-by: Pantelis Antoniou
> ---
> drivers/of/base.c | 7 +++
> drivers
On Wed, Sep 16, 2015 at 07:09:10PM +0300, Pantelis Antoniou wrote:
> The two default overlay attributes are:
>
> * A targets sysfs attribute listing the targets of the installed
> overlay. The targets list the path on the kernel's device tree
> where each overlay fragment is applied to
>
> * A pe
On Sun, Oct 04, 2015 at 08:14:16PM +0100, Greg KH wrote:
>
> Are you sure? I think this should stay as "Userspace..." as that is
> what it does, right?
>
> Turning it off should only drop the userspace callouts, it shouldn't
> stop the kernel from loading firmware from the filesystem all on its
Hi Greg,
Thanks for the response! It's always good to get notes on a patch.
Some responses to your points:
> Why __le32? Does this variable go across the user/kernel boundry
> somehow? If not, just use le32.
Good point, this should probably have been le32.
> At first glance, you aren't doing
On Sun, Oct 04, 2015 at 10:46:05AM -0800, Mike Dupuis wrote:
> > And I think you just broke the "autoload" logic that these "call a null
> > function" function calls were trying to solve, which isn't good at all.
>
> I guess this bit is lost on me-- how does calling a function from a
> previously
On Mon 2015-09-07 17:36:15, Irina Tirdea wrote:
> Signed-off-by: Irina Tirdea
> ---
> drivers/input/touchscreen/goodix.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
Don't.
Yes, we sometimes sort includes... to avoid patch rejects.
This is guaranteed to cause rejects.
Hi!
> Go to grsecurity.org, look on the side panel where it lists the versions, you
> see:
>
> Stable (Restricted): 3.1-3.2.71 Last updated: 09/13/15
> Stable (Restricted): 3.1-3.14.52 Last updated: 09/13/15
> Test (Free): 3.1-4.1.7 Last updated: 09/13/15
>
> What does this mean? It means the
On Tue 2015-09-15 16:03:36, David Howells wrote:
> From: David Woodhouse
>
> The GPL does not permit us to link against the OpenSSL library. Use
> LGPL for sign-file and extract-file instead.
Actually GPL does permit you to link to "system libraries", and it looks like
OpenSSL is pretty much sy
On 2015-10-03 01:05, Peter Rosin wrote:
> I looked around and found that if I revert
> a839ce663b3183209fdf7b1fc4796bfe2a4679c3
> "eeprom: at24: extend driver to allow writing via i2c_smbus_write_byte_data"
> eeprom writing starts working again.
>
> AFAICT, the i2c-at91 bus driver makes the eepro
Hi Peter,
On Thu, Oct 1, 2015 at 2:17 AM, Peter Zijlstra wrote:
> On Thu, Oct 01, 2015 at 08:45:44AM +0200, Stephane Eranian wrote:
>> This patch series extends perf record/report/annotate to enable
>> profiling of jitted (just-in-time compiled) code. The current
>> perf tool provides very limite
Brendan,
On Thu, Oct 1, 2015 at 3:45 PM, Brendan Gregg wrote:
> G'Day,
>
> On Wed, Sep 30, 2015 at 11:45 PM, Stephane Eranian wrote:
>>
>> This patch series extends perf record/report/annotate to enable
>> profiling of jitted (just-in-time compiled) code. The current
>> perf tool provides very l
Fixes commit 810f19bcb862 ("via-rhine: add consistent memory barrier in
vlan receive code.") which broke VLAN tag parsing on receive.
Because eth_type_trans() consumes ethernet header worth of bytes, a call
to read TCI from packet using rhine_rx_vlan_tag() no longer works as it's
reading from an i
On Sun, Oct 04, 2015 at 10:54:57AM +0300, Michael S. Tsirkin wrote:
> On Sat, Oct 03, 2015 at 07:28:07PM -0400, Gabriel L. Somlo wrote:
> > From: Gabriel Somlo
> >
> > Instead of blindly probing fw_cfg registers at known IOport and MMIO
> > locations, use the ACPI subsystem to determine whether a
On Sun, Oct 04, 2015 at 04:24:00PM -0400, Gabriel L. Somlo wrote:
> On Sun, Oct 04, 2015 at 10:54:57AM +0300, Michael S. Tsirkin wrote:
> > On Sat, Oct 03, 2015 at 07:28:07PM -0400, Gabriel L. Somlo wrote:
> > >
> > > Instead of blindly probing fw_cfg registers at known IOport and MMIO
> > > locat
Hello.
Here's a set of 8 patches against the 'usb-next' branch of Greg KH's
'usb.git' repo. It's to eliminate the use of the PCI_DEVICE() macro where
less verbose PCI_VDEVICE() should have been used.
[1/8] ehci-pci: use PCI_VDEVICE() instead of PCI_DEVICE()
[2/8] ohci-pci:-use-PCI_VDEVICE() i
This series add support for MSI and MSI-X interrupts to uio_pci_generic driver.
Currently uio_pci_generic supports only legacy INT#x interrupts source. However
there are situations when this is not enough, for instance SR-IOV VF devices
that
simply don't have INT#x capability. For such devices u
Signed-off-by: Vlad Zolotarov
---
drivers/uio/uio.c | 15 +++
include/linux/uio_driver.h | 3 +++
2 files changed, 18 insertions(+)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 8196581..714b0e5 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -704,6 +70
Change the chapters related to uio_pci_generic that refer interrupt mode.
Add the relevant explanation regarding MSI and MSI-X interrupt modes
support.
Signed-off-by: Vlad Zolotarov
---
Documentation/DocBook/uio-howto.tmpl | 29 ++---
1 file changed, 26 insertions(+), 3 d
Add support for MSI and MSI-X interrupt modes:
- Interrupt mode selection order is:
INT#X (for backward compatibility) -> MSI-X -> MSI.
- Add ioctl() commands:
- UIO_PCI_GENERIC_INT_MODE_GET: query the current interrupt mode.
- UIO_PCI_GENERIC_IRQ_NUM_GET: query the maximu
SCIF depends on IOVA which requires IOMMU_SUPPORT to be enabled.
The long term fix is to move IOVA from drivers/iommu to lib/
but this current patch should fix the reported issue.
Reported-by: Fengguang Wu
Reviewed-by: Ashutosh Dixit
Signed-off-by: Sudeep Dutt
---
drivers/misc/mic/Kconfig | 2
Signed-off-by: Vlad Zolotarov
---
drivers/uio/uio.c | 15 +++
include/linux/uio_driver.h | 3 +++
2 files changed, 18 insertions(+)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 8196581..714b0e5 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -704,6 +70
Add support for MSI and MSI-X interrupt modes:
- Interrupt mode selection order is:
INT#X (for backward compatibility) -> MSI-X -> MSI.
- Add ioctl() commands:
- UIO_PCI_GENERIC_INT_MODE_GET: query the current interrupt mode.
- UIO_PCI_GENERIC_IRQ_NUM_GET: query the maximu
Change the chapters related to uio_pci_generic that refer interrupt mode.
Add the relevant explanation regarding MSI and MSI-X interrupt modes
support.
Signed-off-by: Vlad Zolotarov
---
Documentation/DocBook/uio-howto.tmpl | 29 ++---
1 file changed, 26 insertions(+), 3 d
This series add support for MSI and MSI-X interrupts to uio_pci_generic driver.
Currently uio_pci_generic supports only legacy INT#x interrupts source. However
there are situations when this is not enough, for instance SR-IOV VF devices
that
simply don't have INT#x capability. For such devices u
This is the same v3 but with the correct email address of Greg. In the
first iteration the first letter of the email was missing... ;)
On 10/04/15 23:43, Vlad Zolotarov wrote:
This series add support for MSI and MSI-X interrupts to uio_pci_generic driver.
Currently uio_pci_generic supports o
On 10/04/15 22:03, Greg KH wrote:
On Sun, Oct 04, 2015 at 07:49:35PM +0300, Vlad Zolotarov wrote:
FYI: I've just posted to linux-kernel list patches that add support for both
MSI and MSI-X interrupt modes to uio_pci_generic driver.
It addresses most (all) remarks on this thread and also fixes
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/host/ehci-pci.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: usb/drivers/usb/host/ehci-pci.c
=
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/host/ohci-pci.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
Index: usb/drivers/usb/host/ohci-pci.c
=
On 10/03/2015 06:19 PM, Nicholas Krause wrote:
This fixes the locking region in the function brcmf_sdio_sendfromq
to properly lock around the call to the function brcmrf_sdio_txpkt
in order to avoid concurrent access issues when calling this
function as stated in the function's comments about the
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/chipidea/ci_hdrc_pci.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: usb/drivers/usb/chipidea/ci_hdrc_pci.c
===
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/dwc2/pci.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Index: usb/drivers/usb/dwc2/pci.c
===
On Wed, Sep 30, 2015 at 9:01 AM, wrote:
> This interface has no current users and is obsolete.
mmm, how does Sean's madeye util is working?
Or.
--
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 a
On 10/03/2015 06:24 AM, Nicholas Krause wrote:
This uses the proper skb wrapper function sk_unlink in the function
brcmf_sdio_txpkt_postp to properly protect against concurrent users
accessing this skb_buff pointer or skb_buff_head pointer by locking
the spinlock as part of the passed skb_buff_he
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/dwc3/dwc3-pci.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
Index: usb/drivers/usb/dwc3/dwc3-pci.c
=
On Sat, 3 Oct 2015, Felipe Balbi wrote:
> > The WiiU adapter from Mayflash (see
> > http://www.mayflash.com/Products/NINTENDOWiiU/W009.html) is not
> > working correctly.
> >
> > The "XInput" mode works fine, the controller is recognized as a xbox
> > controller. But it is only possible to conn
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/gadget/udc/amd5536udc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: usb/drivers/usb/gadget/udc/amd5536udc.c
===
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/gadget/udc/pch_udc.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
Index: usb/drivers/usb/gadget/udc/pch_udc.c
Fix using the PCI_DEVICE() macro instead of less verbose PCI_VDEVICE().
Signed-off-by: Sergei Shtylyov
---
drivers/usb/gadget/udc/bdc/bdc_pci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: usb/drivers/usb/gadget/udc/bdc/bdc_pci.c
=
Le 02/10/2015 15:57, Nicolas Ferre a écrit :
> Hi all,
>
> Well it seems my cover letter is missing. So, here it is:
>
> ---8<
> pinctrl: at91-pio4: fixes for current linux-next (irq)
>
> While testing the sama5d2 on today's linux-next I discovered that some
> adaptations were missing. So, I
+ Rafal (to extend this mighty CC list)
On Fri, Oct 02, 2015 at 11:26:44PM +0530, Anup Patel wrote:
> The BRCM NAND controller on NS2 SoC requires a reset to
> cleanup previously configured NAND controller state.
>
> This patch adds optional boolean device tree flag named
> "brcm,nand-iproc-reset
Commit 63692df1 ("PCI: Allow numa_node override via sysfs") didn't check that
the numa node provided by userspace is valid. Passing a node number too high
would attempt to access invalid memory and trigger a kernel panic.
Fixes: 63692df1 ("PCI: Allow numa_node override via sysfs")
Signed-off-by: S
On 10/03/2015 10:24 AM, Ingo Molnar wrote:
...
Feel free to send a patch that adds a sentence to that help text that explains
that this is an internal helper Kconfig entry that does not need to be
interactively configurable.
Sorry for the late reply. I think it's actually fine as-is, noticed th
Before the previous patch, __mem_cgroup_from_kmem had to handle two
types of kmem - slab pages and pages allocated with alloc_kmem_pages -
differently, because slab pages did not store information about owner
memcg in the page struct. Now we can unify it. Since after it, this
function becomes tiny
We have memcg_kmem_charge and memcg_kmem_uncharge methods for charging
and uncharging kmem pages to memcg, but currently they are not used for
charging slab pages (i.e. they are only used for charging pages
allocated with alloc_kmem_pages). The only reason why the slab subsystem
uses special helper
Charging kmem pages proceeds in two steps. First, we try to charge the
allocation size to the memcg the current task belongs to, then we
allocate a page and "commit" the charge storing the pointer to the memcg
in the page struct.
Such a design looks overcomplicated, because there is no much sense
Noticed that commit a20135ffbc44 ("writeback: don't drain
bdi_writeback_congested on bdi destruction") added a usage of
rbtree_postorder_for_each_entry_safe() in mm/backing-dev.c which appears
to try to rb_erase() elements from an rbtree while iterating over it
using rbtree_postorder_for_each_entry
101 - 200 of 276 matches
Mail list logo
