lp:~kamalmostafa/ubuntu/+source/linux/+git/trusty

Owned by Kamal Mostafa
Get this repository:
git clone https://git.launchpad.net/~kamalmostafa/ubuntu/+source/linux/+git/trusty
Only Kamal Mostafa can upload to this repository. If you are Kamal Mostafa please log in for upload directions.

Branches

Name Last Modified Last Commit
master 2018-08-10 14:19:10 UTC 2018-08-10
UBUNTU: Ubuntu-3.13.0-155.205

Author: Juerg Haefliger
Author Date: 2018-08-10 14:19:10 UTC

UBUNTU: Ubuntu-3.13.0-155.205

Signed-off-by: Juerg Haefliger <juergh@canonical.com>

lp1720867-nvmemsi 2017-10-04 17:31:55 UTC 2017-10-04
NVMe: Always use MSI/MSI-x interrupts

Author: Keith Busch
Author Date: 2016-07-19 21:36:59 UTC

NVMe: Always use MSI/MSI-x interrupts

BugLink: http://bugs.launchpad.net/bugs/1720867

Multiple users have reported device initialization failure due the driver
not receiving legacy PCI interrupts. This is not unique to any particular
controller, but has been observed on multiple platforms.

There have been no issues reported or observed when with message signaled
interrupts, so this patch attempts to use MSI-x during initialization,
falling back to MSI. If that fails, legacy would become the default.

The setup_io_queues error handling had to change as a result: the admin
queue's msix_entry used to be initialized to the legacy IRQ. The case
where nr_io_queues is 0 would fail request_irq when setting up the admin
queue's interrupt since re-enabling MSI-x fails with 0 vectors, leaving
the admin queue's msix_entry invalid. Instead, return success immediately.

Reported-by: Tim Muhlemmer <muhlemmer@gmail.com>
Reported-by: Jon Derrick <jonathan.derrick@intel.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
(back ported from commit a5229050b69cfffb690b546c357ca5a60434c0c8)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

 Conflicts:
 drivers/nvme/host/pci.c

Acked-by: Brad Figg <brad.figg@canonical.com>
Signed-off-by: Kamal Mostafa <kamal@canonical.com>
(kamal: back ported from 90c9712fbb@ubuntu-xenial.git)

master-next 2017-09-19 11:14:28 UTC 2017-09-19
UBUNTU: Ubuntu-3.13.0-133.182

Author: Juerg Haefliger
Author Date: 2017-09-19 11:14:28 UTC

UBUNTU: Ubuntu-3.13.0-133.182

Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>

ena120 2017-06-30 14:40:47 UTC 2017-06-30
net: ena: update ena driver to version 1.2.0

Author: Netanel Belgazal
Author Date: 2017-06-23 08:22:00 UTC

net: ena: update ena driver to version 1.2.0

BugLink: http://bugs.launchpad.net/bugs/1701575

Signed-off-by: Netanel Belgazal <netanel@amazon.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 8523899912b6958ef471d2393c016f87dc4f0354 net-next)
Signed-off-by: Kamal Mostafa <kamal@canonical.com>

ena112 2017-03-28 18:31:10 UTC 2017-03-28
net/ena: update driver version to 1.1.2

Author: Netanel Belgazal
Author Date: 2017-02-13 23:10:10 UTC

net/ena: update driver version to 1.1.2

BugLink: http://bugs.launchpad.net/bugs/1664312

Signed-off-by: Netanel Belgazal <netanel@annapurnalabs.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 3e5d6897176d38b54124da56183810abbd68c8bc)
Signed-off-by: Kamal Mostafa <kamal@canonical.com>

ena-trusty 2016-10-21 20:48:23 UTC 2016-10-21
UBUNTU: [config] enable CONFIG_ENA_ETHERNET=m (Amazon ENA driver)

Author: Kamal Mostafa
Author Date: 2016-08-26 16:56:45 UTC

UBUNTU: [config] enable CONFIG_ENA_ETHERNET=m (Amazon ENA driver)

BugLink: http://bugs.launchpad.net/bugs/1635721

Signed-off-by: Kamal Mostafa <kamal@canonical.com>

lp994931-ipv6 2016-09-16 16:24:50 UTC 2016-09-16
neigh: ipv6: respect default values set before an address is assigned to device

Author: Jiri Pirko
Author Date: 2013-12-07 18:26:57 UTC

neigh: ipv6: respect default values set before an address is assigned to device

commit bba24896f022d4d239494bebf18e713cd8aec7a5 upstream.

Make the behaviour similar to ipv4. This will allow user to set sysctl
default neigh param values and these values will be respected even by
devices registered before (that ones what do not have address set yet).

Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Signed-off-by: David S. Miller <davem@davemloft.net>
BugLink: https://bugs.launchpad.net/bugs/994931
Signed-off-by: Kamal Mostafa <kamal@canonical.com>

fix-stackprotector 2015-12-11 19:21:26 UTC 2015-12-11
Revert "UBUNTU: SAUCE: disable stack-protector for ARM compressed bootloader"

Author: Kamal Mostafa
Author Date: 2015-12-09 20:40:48 UTC

Revert "UBUNTU: SAUCE: disable stack-protector for ARM compressed bootloader"

This reverts commit 900be9e1bdc70f08ee67326254e1f340fba09541.

This SAUCE is no longer needed, since these commits fix the broken
stack-protector logic in arch/arm/Makefile:

stackprotector: Introduce CONFIG_CC_STACKPROTECTOR_STRONG
stackprotector: Unify the HAVE_CC_STACKPROTECTOR logic between architectures

Signed-off-by: Kamal Mostafa <kamal@canonical.com>

18 of 8 results
This repository contains Public information 
Everyone can see this information.

Subscribers