UBUNTU: Start new release

Ignore: yes
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: [packaging] we already have a valid src_pkg_name

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: [packaging] allow us to select which builds have uefi signed versions

Signed-off-by: Andy Whitcroft <apw@canonical.com>
UBUNTU: SAUCE: input: fix weird issue of synaptics psmouse sync lost after resume

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

From: Eric Miao <eric.miao@canonical.com>

This patch has already been sent upstream by Eric. Unfortunately,
after a little back and forth between Eric and Dmitry Torokhov, the
patch did get included, and there is still an open question to Dmitry.

However, this is a known issue on at least 4 systems, and it causes
them to lose their mouse device on suspend. So I was hoping we could
get it in to quantal. Original email follows:

So in summary, the symptom is intermittent key events lost after resume
on some machines with synaptics touchpad (seems this is synaptics _only_),
and key events loss is due to serio port reconnect after psmouse sync lost.
Removing psmouse and inserting it back during the suspend/resume process
is able to work around the issue, so the difference between psmouse_connect()
and psmouse_reconnect() is the key to the root cause of this problem.

After comparing the two different paths, synaptics driver has its own
implementation of synaptics_reconnect(), and the missing psmouse_probe()
seems significant, the patch below added psmouse_probe() to the reconnect
process, and has been verified many times that the issue could not be reliably
reproduced.

There are two PS/2 commands in psmouse_probe():

  1. PSMOUSE_CMD_GETID
  2. PSMOUSE_CMD_RESET_DIS

The weird thing is, the PSMOUSE_CMD_GETID seems to be significant, and the
PSMOUSE_CMD_RESET_DIS is irrelevant to this issue after trying several times.
Now it's rather difficult to form a sane theory. So this patch is
really for RFC.
Note it does fix a real problem though.

http://thread.gmane.org/gmane.linux.kernel.input/25599
Signed-off-by: James M Leddy <james.leddy@canonical.com>
Acked-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: SAUCE: Bluetooth: Remove rules for matching Broadcom vendor specific IDs

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

Since the Broadcom devices with vendor specific IDs [0x0a5c:*]
can be matched by USB_VENDOR_AND_INTERFACE_INFO(0x0a5c...),
remove old rules that is not needed any more.

Signed-off-by: Wen-chien Jesse Sung <jesse.sung@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Bluetooth: Add USB_VENDOR_AND_INTERFACE_INFO() for Broadcom/Foxconn

BugLink: https://launchpad.net/bugs/1030233

Foxconn devices has a vendor specific class of device, we will match them
differently now.

Cc: stable@vger.kernel.org
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
(cherry picked from commit ee66401bb94b1f2ce51089c341dcdd25d26ae631 upstream)
Signed-off-by: Wen-chien Jesse Sung <jesse.sung@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: SAUCE: net/ipv4: Always flush route cache on unregister batch call

When doing (for example) a connect to an unused port on localhost
in a new net namespace, it was observed that lo could not be
removed immediately because there were still references on it.
To release those references could take a very long time (up to
five minutes).

This was tracked down to an element in the route cache which was
supposed to be dropped by a notify call with sending a
NETDEVICE_UNREGISTER_BATCH message, but as in_dev is already unset
then, the case statement never was executed.

Move the handling of that notification up to be done regardless of
the state of in_dev.

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

Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: SAUCE: omap3 clocks .dev_id = NULL

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

Signed-off-by: Joe Woodward <jw@terrafix.co.uk>
Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
Acked-by: Andy Whitcroft <andy.whitcroft@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: [Config] omap: disable USB_[EHCI|OHCI]_HCD_PLATFORM

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

Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
Acked-by: Andy Whitcroft <andy.whitcroft@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: [Config] omap: enforce USB_[EHCI|OHCI]_HCD_PLATFORM=n

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

Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
Acked-by: Andy Whitcroft <andy.whitcroft@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
UBUNTU: Temporarily disable module check on build

We've purposelly disabled some modules:

  UBUNTU: [Config] omap: disable USB_[EHCI|OHCI]_HCD_PLATFORM

Purposely disable the module check to avoid build failures.

Ignore: yes
Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
UBUNTU: Ubuntu-3.5.0-17.28

Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>