On Tue, May 7, 2013 at 9:14 AM, Kim, Milo wrote:
> Currently, the LP55xx DT structure supports max 3 channels.
> However, LP5523 has max 9 channels and LP5562 has 4 channels.
> To enhance this constraint, the DT structure has been changed.
>
> (a) Use the child node for various channel settings
This reduces the size of the stack frame when calling request_module().
Performing the sprintf before the call is not needed.
Signed-off-by: Kees Cook
---
drivers/mtd/chips/gen_probe.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/mtd/chips/gen_probe.c
This reduces the size of the stack frame when calling request_module().
Performing the sprintf before the call is not needed.
Signed-off-by: Kees Cook
---
drivers/gpu/drm/drm_encoder_slave.c |6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git
On Tue, May 07, 2013 at 04:18:23PM +0200, Jiri Slaby wrote:
> From: Jeff Mahoney
>
> The PCH EG20T is only compatible with Intel Atom processors so it
> should depend on x86.
This patch has been submitted before,
https://patchwork.kernel.org/patch/2069071/
and at that time the reaction was
On Tue, May 07, 2013 at 07:14:48PM +, Shuah Khan wrote:
>
> > From: Greg Kroah-Hartman
> > Date: Mon, May 6, 2013 at 4:58 PM
> > Subject: [ 00/46] 3.0.77-stable review
> > To: linux-kernel@vger.kernel.org
> > Cc: Greg Kroah-Hartman ,
> > torva...@linux-foundation.org,
From: David Daney
There are several parts to this:
o All registers are 64-bits wide, 32-bit guests use the least
significant portion of the register storage fields.
o FPU register formats are defined.
o CP0 Registers are manipulated via the KVM_GET_MSRS/KVM_SET_MSRS
mechanism.
The
> Date: Mon, May 6, 2013 at 4:55 PM
> Subject: [ 00/63] 3.4.44-stable review
> To: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman ,
> torva...@linux-foundation.org, a...@linux-foundation.org,
> sta...@vger.kernel.org
>
>
> This is the start of the stable review cycle for the 3.4.44
> From: Greg Kroah-Hartman
> Date: Mon, May 6, 2013 at 5:11 PM
> Subject: [ 000/104] 3.8.12-stable review
> To: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman ,
> torva...@linux-foundation.org, a...@linux-foundation.org,
> sta...@vger.kernel.org
>
>
> This is the start of the stable
A couple of fixes + getting rid of __blkdev_put() return value.
Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (4):
hfs: SMP race on directory close()
mtd_blktrans_ops->release() should return void
> From: Greg Kroah-Hartman
> Date: Mon, May 6, 2013 at 4:58 PM
> Subject: [ 00/46] 3.0.77-stable review
> To: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman ,
> torva...@linux-foundation.org, a...@linux-foundation.org,
> sta...@vger.kernel.org
>
>
> This is the start of the stable
> From: Greg Kroah-Hartman
> Date: Mon, May 6, 2013 at 2:43 PM
> Subject: [ 000/115] 3.9.1-stable review
> To: linux-kernel@vger.kernel.org
> Cc: Greg Kroah-Hartman ,
> torva...@linux-foundation.org, a...@linux-foundation.org,
> sta...@vger.kernel.org
>
>
> NOTE: I have NOT applied all of the
On Tue, May 07, 2013 at 12:27:11PM -0600, Jason Gunthorpe wrote:
> On Tue, May 07, 2013 at 09:15:00AM -0400, Eduardo Valentin wrote:
> > > But broadly the direction seems that drivers should have minimal
> > > dependencies so, eg, the thermal maintainer compiling for x86 should
> > > be able to
On Tue, May 7, 2013 at 9:59 AM, Artem S. Tashkinov wrote:
> May 7, 2013 09:25:40 PM,Bjorn Helgaas wrote:
>> [+cc Phillip]
>>
>>> I would suspect that Windows' complaint about the BIOS mucking up the MTRRs
>>> is likely the best hint. Likely Windows is detecting the problem and fixing
>>>
On May 7, 2013, at 6:18 PM, Jiri Slaby wrote:
> From: Jeff Mahoney
>
> Commit 634725a92938b0f282b17cec0b007dca77adebd2 removed the BUG_ON in
> hfs_bnode_create in hfsplus. This patch removes it from the hfs
> version and avoids an fsfuzzer crash.
>
> Signed-off-by: Jeff Mahoney
> Acked-by:
On Mon, May 06, 2013 at 08:59:37AM -0400, Konrad Rzeszutek Wilk wrote:
>
> Hey,
>
> As I was fixing the PV HVM's broken CPU hotplug mechanism I discovered
> a deadlock in the microcode and generic code.
>
> I am not sure if the ACPI generic mechanism would expose this, but
> looking at the flow
On Wed, May 08, 2013 at 02:47:34AM +0800, Wang YanQing wrote:
> I meet emacs hang in start if I do the operation below:
> 1: echo 3 > /proc/sys/vm/drop_caches
> 2: emacs BigFile
> 3: Press CTRL-S follow 2 immediately
>
> Then emacs hang on, CTRL-Q can't resume, the terminal
> hang on, you
On Tue, May 7, 2013 at 11:50 AM, Artem S. Tashkinov wrote:
> May 7, 2013 10:27:30 PM, Bjorn Helgaas wrote:
> On Tue, May 7, 2013 at 8:59 AM, Artem S. Tashkinov wrote:
>>> May 7, 2013 09:25:40 PM,Bjorn Helgaas wrote:
[+cc Phillip]
> I would suspect that Windows' complaint
May 7, 2013 10:27:30 PM, Bjorn Helgaas wrote:
On Tue, May 7, 2013 at 8:59 AM, Artem S. Tashkinov wrote:
>> May 7, 2013 09:25:40 PM,Bjorn Helgaas wrote:
>>> [+cc Phillip]
>>>
I would suspect that Windows' complaint about the BIOS mucking up the MTRRs
is likely the best hint.
I meet emacs hang in start if I do the operation below:
1: echo 3 > /proc/sys/vm/drop_caches
2: emacs BigFile
3: Press CTRL-S follow 2 immediately
Then emacs hang on, CTRL-Q can't resume, the terminal
hang on, you can do nothing with this terminal except
close it.
The reason is before
On 05/06/2013 11:05 PM, Kevin Cernekee wrote:
On Mon, May 6, 2013 at 10:25 PM, H. Peter Anvin wrote:
Hello,
The touchpad on Lenovo Yoga 13 seems to have broken some time between 3.4
and the current kernel. The dmesg is full of spewage:
[ 256.246481] atkbd serio0: Use 'setkeycodes e03e ' to
On Tuesday 07 May 2013, Linus Torvalds wrote:
> On Tue, May 7, 2013 at 10:26 AM, Arnd Bergmann wrote:
> >
> > Here are the same pull requests as before, with numbers and distinct
> > time stamps. I hope I didn't screw up in a different way this time.
>
> Ok, I notice that you seem to have
On Tue, May 07, 2013 at 01:35:36PM -0400, Peter Hurley wrote:
> On 05/07/2013 11:04 AM, Dave Jones wrote:
> > On Tue, May 07, 2013 at 10:14:09AM -0400, Peter Hurley wrote:
> >
> > > >> Just hit this again, by switching tty's during bootup.
> > > >> The previous time was switching from X
On Tue, May 07, 2013 at 09:15:00AM -0400, Eduardo Valentin wrote:
> > But broadly the direction seems that drivers should have minimal
> > dependencies so, eg, the thermal maintainer compiling for x86 should
> > be able to compile test/static analyze your driver..
> Well, I do not see much of
>
> Joseph, if there's no hardware switch for the wireless on your G770, you can
> probably still take wireless out of the picture by removing or renaming the
> bcma module (look in /lib/modules/.../kernel/drivers/bcma/), then rebooting.
>
> Xiong, do you have a specific network manager-related
The patch 9f81abdac362: "mei: implement mei_cl_connect function"
from Jan 8, 2013, leads to the following static checker warning:
"drivers/misc/mei/main.c:522 mei_ioctl_connect_client()
warn: check 'dev->me_clients[]' for negative offsets (-2)"
Reported-by: Dan Carpenter
Cc:
Quoting Miklos Szeredi (mik...@szeredi.hu):
> From: Miklos Szeredi
>
> The PID and the TGID of the process tringgering the mount are sent to the
> daemon. Currently the global pid values are sent (ones valid in the initial
> pid
> namespace) but this is wrong if the autofs daemon itself is not
Hello,
On Mon, May 06, 2013 at 04:50:05PM -0700, Colin Cross wrote:
> On slow cpus the large number of task wakeups and context switches
> triggered by freezing and thawing tasks can take a significant amount
> of cpu time. This patch series reduces the amount of work done during
> freezing
Quoting Miklos Szeredi (mik...@szeredi.hu):
> From: Sukadev Bhattiprolu
>
> This patch enables autofs4 to work in a "container". oz_pgrp is converted
> from
> pid_t to struct pid and this is stored at mount time based on the "pgrp="
> option
> or if the option is missing then the current
On Tue, 7 May 2013 10:52:05 -0700
Colin Cross wrote:
> CIFS calls wait_event_freezekillable_unsafe with a VFS lock held,
> which is unsafe and will cause lockdep warnings when 6aa9707
> "lockdep: check that no locks held at freeze time" is reapplied
> (it was reverted in dbf520a). CIFS
From: David Daney
As reported:
This problem was discovered when doing BGP traffic with the TCP MD5 option
activated, where the following call chain caused a crash:
* tcp_v4_rcv
* tcp_v4_timewait_ack
* tcp_v4_send_ack -> follow stack variable rep.th
*tcp_v4_md5_hash_hdr
On 05/07/2013 07:08 PM, Randy Dunlap wrote:
> On 05/06/13 20:49, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v3.11 destined work to your linux-next included
>> branches until after v3.10-rc1 is released.
>>
>> I am receiving a (un)reasonable number of conflicts from there being
On Tue, May 7, 2013 at 10:26 AM, Arnd Bergmann wrote:
>
> Here are the same pull requests as before, with numbers and distinct
> time stamps. I hope I didn't screw up in a different way this time.
Ok, I notice that you seem to have forgotten the "--summary" flag from
your diffstat in your new
It doesn't apply anymore. It was against v3.4.
I will send one against Linus' tree soon.
David Daney
On 05/07/2013 10:23 AM, David Daney wrote:
From: David Daney
As reported:
This problem was discovered when doing BGP traffic with the TCP MD5 option
activated, where the following
Hello.
On 07-05-2013 13:49, Sebastian Hesselbarth wrote:
of_mdiobus_register creates a phy_device even if get_phy_device failed
to create it previously. This causes indefinite polling on non-existent
PHYs. This fix makes of_mdio_register rely on get_phy_device to
properly create the device or
CIFS calls wait_event_freezekillable_unsafe with a VFS lock held,
which is unsafe and will cause lockdep warnings when 6aa9707
"lockdep: check that no locks held at freeze time" is reapplied
(it was reverted in dbf520a). CIFS shouldn't be doing this, but
it has long-running syscalls that must
On Tue, May 7, 2013 at 3:07 AM, Jeff Layton wrote:
> On Mon, 6 May 2013 16:50:07 -0700
> Colin Cross wrote:
>
>> CIFS calls wait_event_freezekillable_unsafe with a VFS lock held,
>> which is unsafe and will cause lockdep warnings when 6aa9707
>> "lockdep: check that no locks held at freeze
On Tue, May 7, 2013 at 10:32 AM, Russell King - ARM Linux
wrote:
>
> So I don't think that asking people to play games with delays between
> consecutive messages is going to work all that well.
Actually, since this has happened before (a lot) with patch series,
I'm pretty sure it helps.
I used
On Tuesday 07 May 2013, Russell King - ARM Linux wrote:
> On Tue, May 07, 2013 at 10:02:22AM -0700, Linus Torvalds wrote:
> > So you seem to have blasted this series out with that automated
> > script, so they all got sent basically at the same timestamp, and they
> > are in the wrong order in my
Hello, Linus, Jeff, linux-ide folks.
As discussed earlier, Jeff is leaving for something more fun and I'm
inheriting the maintainership of libata. Please pull from the
following branch to receive MAINTAINERS update.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git for-3.10
I'll
On 05/07/2013 11:04 AM, Dave Jones wrote:
On Tue, May 07, 2013 at 10:14:09AM -0400, Peter Hurley wrote:
> >> Just hit this again, by switching tty's during bootup.
> >> The previous time was switching from X to console iirc, so that seems to
be
> >> the key to triggering this.
> >
>
Hello.
On 07-05-2013 21:19, Tejun Heo wrote:
As discussed earlier, Jeff is leaving for something more fun and I'm
inheriting the maintainership of libata. Please pull from the
following branch to receive MAINTAINERS update.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git
On Tue, May 07, 2013 at 10:02:22AM -0700, Linus Torvalds wrote:
> So you seem to have blasted this series out with that automated
> script, so they all got sent basically at the same timestamp, and they
> are in the wrong order in my mailbox because email isn't that ordered.
Interesting. What I
On 05/07/2013 09:46 AM, Jiang Liu wrote:
Hi Eunsong,
Thanks for your help. I have done some code inspection and have
found a possible reason for this issue. It seems that virt_to_page()
can't be used to handle address in compatible segments due to following
definitions.
This has caused
These are mostly new device tree bindings for existing drivers, as well
as changes to the device tree source files to add support for those
devices, and a couple of new boards, most notably Samsung's Exynos5
based Chromebook.
The changes depend on earlier platform specific updates and touch
the
These are cleanups and smaller changes that either depend on earlier
feature branches or came in late during the development cycle.
We normally try to get all cleanups early, so these are the exceptions:
- A follow-up on the clocksource reworks, hopefully the last time
we need to merge
These continue the multiplatform support for exynos, adding support
for building most of the essential drivers (clocksource, clk, irqchip)
when combined with other platforms. As a result, it should become
really easy to add full multiplatform exynos support in 3.11, although
we don't yet enable it
This is the third and smallest of the SoC specific updates.
Changes include:
* SMP support for the Xilinx zynq platform
* Smaller imx changes
* LPAE support for mvebu
* Moving the orion5x, kirkwood, dove and mvebu platforms
to a common "mbus" driver for their internal devices.
It would be good
These patches are all for Renesas shmobile, and depend on the earlier
pinctrl updates. Remarkably, this adds support for three new SoCs:
r8a73a4, r8a73a4 and r8a7778. The bulk of the code added for these is
for pinctrl (using the new subsystem) and for clocks (not yet using the
common clock
Hi Linus,
Here are the same pull requests as before, with numbers and distinct
time stamps. I hope I didn't screw up in a different way this time.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
From: David Daney
As reported:
This problem was discovered when doing BGP traffic with the TCP MD5 option
activated, where the following call chain caused a crash:
* tcp_v4_rcv
* tcp_v4_timewait_ack
* tcp_v4_send_ack -> follow stack variable rep.th
*tcp_v4_md5_hash_hdr
On Mon, May 06, 2013 at 05:00:39PM -0700, Hugh Dickins wrote:
> On Mon, 6 May 2013, Greg Kroah-Hartman wrote:
>
> > 3.9-stable review patch. If anyone has any objections, please let me know.
>
> NAK to 067/115 for 3.9, 063/104 for 3.8 and 38/63 for 3.4: they duplicate
>036/115 for 3.9,
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various
On Tuesday 07 May 2013, Linus Torvalds wrote:
> On Tue, May 7, 2013 at 9:02 AM, Arnd Bergmann wrote:
> >
> > I used a new script to create the pull requests this time, hope
> > I got it right now.
>
> So you seem to have blasted this series out with that automated
> script, so they all got sent
On Tue, May 07, 2013 at 02:56:29PM +1000, Michael D. Setzer II wrote:
> On 6 May 2013 at 19:47, Greg KH wrote:
>
> Date sent:Mon, 6 May 2013 19:47:50 -0700
> From: Greg KH
> To: "Michael D. Setzer II"
> Copies to:
Hello, Linus, Jeff, linux-ide folks.
As discussed earlier, Jeff is leaving for something more fun and I'm
inheriting the maintainership of libata. Please pull from the
following branch to receive MAINTAINERS update.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git for-3.10
I'll
* John Stultz wrote:
> On 05/06/2013 11:53 PM, Ingo Molnar wrote:
> >* Feng Tang wrote:
> >
> >>>is even worse than that. Machine can stay is s2ram for weeks (for a
> >>>lot more if it is desktop and you do s2ram for powersaving). Also
> >>>temperature of CPU varies a lot between active and
* Waiman Long wrote:
> On 05/07/2013 03:01 AM, Ingo Molnar wrote:
> >* Waiman Long wrote:
> >
> >>When "perf record" was used on a large machine with a lot of CPUs,
> >>the perf post-processing time could take a lot of minutes and even
> >>hours depending on how large the resulting perf.data
On Tue, 2013-05-07 at 09:20 -0700, Bjorn Helgaas wrote:
> [+cc Eric because he made a change (69b08f62e17) that apparently
> exposes driver bugs]
>
> On Mon, May 6, 2013 at 7:51 PM, Huang, Xiong wrote:
> >> >
> >> > Did this ever get resolved?
> >>
> >> I opened
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various
On Tue, May 7, 2013 at 9:02 AM, Arnd Bergmann wrote:
>
> I used a new script to create the pull requests this time, hope
> I got it right now.
So you seem to have blasted this series out with that automated
script, so they all got sent basically at the same timestamp, and they
are in the wrong
On 05/06/2013 11:30 PM, EUNBONG SONG wrote:
>
> Hello. I tested with two patches.
> The first one is thomas gleixner's patch. The patch is as follow.
> This patch works well without any problem.
You don't need them both. When we fix it, it will be one or the other,
not both.
>
> Index:
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various
On 7 May 2013 07:28, Rob Herring wrote:
> On 05/06/2013 02:24 AM, Jassi Brar wrote:
>> Convert the PL320 controller driver to work with the common
>> mailbox API. Also convert the only user of PL320, highbank-cpufreq.c
>> to work with thee API. Drop the obsoleted driver pl320-ipc.c
>>
>>
With the recent updates, blk-throttle is finally ready for proper
hierarchy support. Dispatching now honors service_queue->parent_sq
and propagates correctly. The only thing missing is setting
->parent_sq correctly so that throtl_grp hierarchy matches the cgroup
hierarchy.
This patch updates
Hi Eunsong,
Thanks for your help. I have done some code inspection and have
found a possible reason for this issue. It seems that virt_to_page()
can't be used to handle address in compatible segments due to following
definitions.
#define virt_to_page(kaddr)
On Tue, May 7, 2013 at 7:08 AM, Alex Deucher wrote:
> On Mon, May 6, 2013 at 7:39 PM, Andy Lutomirski wrote:
>> On Mon, May 6, 2013 at 4:04 PM, Jerome Glisse wrote:
>>> On Mon, May 6, 2013 at 5:22 PM, Andy Lutomirski wrote:
On Fri, May 3, 2013 at 4:00 PM, Andy Lutomirski
wrote:
Ralf Baechle writes:
> cobalt_defconfig:
>
> CC [M] drivers/hid/usbhid/hid-quirks.o
> LD [M] drivers/hid/usbhid/usbhid.o
> FATAL: drivers/hid/usbhid/usbhid: sizeof(struct usb_device_id)=32 is not a
> modulo of the size of section __mod_usb_device_table=48.
> Fix definition of struct
On Wed, 2013-04-24 at 13:58 +0900, Takao Indoh wrote:
> This patch resets PCIe devices on boot to stop ongoing DMA. When
> "pci=pcie_reset_devices" is specified, a hot reset is triggered on each
> PCIe root port and downstream port to reset its downstream endpoint.
>
> Problem:
> This patch
On 05/07/2013 06:57 AM, Pavel Machek wrote:
So I guess it should go through the timekeeping tree...?
I would prefer that, but we can also take it through arm-soc, it doesn't
really matter.
I see no response from timekeeping people... so if you could take it,
that would be great.
I don't
On Mon, May 06, 2013 at 03:09:55PM +0200, Michael Holzheu wrote:
> Hello Vivek,
>
> For s390 we want to use /proc/vmcore for our SCSI stand-alone
> dump (zfcpdump). We have support where the first HSA_SIZE bytes are
> saved into a hypervisor owned memory area (HSA) before the kdump
> kernel is
On 05/07/2013 12:59 AM, Mika Westerberg wrote:
On Mon, May 06, 2013 at 04:11:03PM -0700, David Cohen wrote:
When DT is not used IOAPIC does not register irq domain. As result
IOAPIC won't care about gpio-langwell's virq and may cause conflict if
an irq number is equal to gpio-langwell's virq
On Tue, Apr 30, 2013 at 10:25:41AM -0700, Kees Cook wrote:
> To fix /dev/kmsg, let's compare the existing interfaces and what they allow:
>
> - /proc/kmsg allows:
> - open (SYSLOG_ACTION_OPEN) if CAP_SYSLOG since it uses a destructive
>single-reader interface (SYSLOG_ACTION_READ).
> -
On Tue, May 7, 2013 at 8:59 AM, Artem S. Tashkinov wrote:
> May 7, 2013 09:25:40 PM,Bjorn Helgaas wrote:
>> [+cc Phillip]
>>
>>> I would suspect that Windows' complaint about the BIOS mucking up the MTRRs
>>> is likely the best hint. Likely Windows is detecting the problem and fixing
>>>
[+cc Eric because he made a change (69b08f62e17) that apparently
exposes driver bugs]
On Mon, May 6, 2013 at 7:51 PM, Huang, Xiong wrote:
>> >
>> > Did this ever get resolved?
>>
>> I opened https://bugzilla.kernel.org/show_bug.cgi?id=57681 to keep track of
>> this and attached the dmesg logs
Hi Konrad,
On 05/06/2013 10:35 AM, Konrad Rzeszutek Wilk wrote:
>>> e.g. if a VCPU sets a timer for NOW+5, but 3 are stolen in the middle it
>>> would not make sense (from the guests PoV) for NOW'==NOW+2 at the point
>>> where the timer goes off. Nor does it make sense to require that the
>>>
Ping?
Thanks,
Sasha
On 04/30/2013 02:54 PM, Sasha Levin wrote:
> liblockdep is a tiny wrapper built around kernel/lockdep.c. The aim is to
> provide the same functionality the kernel gets from lockdep to userspace.
>
> The bulk of the code here is the LD_PRELOAD support which provides users
>
Hello, Vivek.
On Tue, May 07, 2013 at 09:55:11AM -0400, Vivek Goyal wrote:
> So if somebody does not specify __DEVEL_sane_behavior, hierarchy is
> still broken. Should we continue to display the message in that case?
The message is to warn people of possible behavior changes. For
blk-throttle,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/7/2013 11:25 AM, Bjorn Helgaas wrote:
> Phillip, I cc'd you because you have similar hardware and your
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1131468 report
> is slightly similar. Have you seen anything like this "reduced
>
Jake reported that since commit 1672c0e31917f49d31d30d79067103432bc20cc7
"mac80211: start auth/assoc timeout on frame status", he is unable to
connect to his AP, which is configured to use passive channel.
After switch to passive channel 4965 firmware drops any TX packet until
it receives beacon.
Ok. Thanks but actually I wanted to get idea how to create kernel
patch and how to use GIT. So now will try to focus on actual fix.
Anyways sorry for any inconvenience occured due to whitespace
messaging patch.
Thanks a lot again.
On Tue, May 7, 2013 at 9:00 PM, H. Peter Anvin wrote:
> On
On Tue, May 07, 2013 at 01:09:14PM +, Kim, Milo wrote:
> For better power efficiency, regulator subsystem provides operating mode.
> (fast, normal, idle and standby)
> The operating mode is selective by a regulator consumer.
>
> With this patch, regulator operating mode can be set in the DT
On Tue, 7 May 2013 16:54:23 +0500
Syed Salman Mansoor wrote:
> I am a newbie and trying to learn so that I can contribute whatever I can.
If you have not already done so, please have a look at:
Documentation/HOWTO
Documentation/development-process
both of which can be found in
These patches are all for Renesas shmobile, and depend on the earlier
pinctrl updates. Remarkably, this adds support for three new SoCs:
r8a73a4, r8a73a4 and r8a7778. The bulk of the code added for these is
for pinctrl (using the new subsystem) and for clocks (not yet using the
common clock
Hi Linus,
This is the third and final batch of branches for arm-soc for the
3.10 merge window. Following what Olof did earlier, I pushed out
a branch with the conflicts resolved named 'third-batch-resolved'
for reference.
We still have a bunch of outstanding bug fixes that we'll send
later this
These are mostly new device tree bindings for existing drivers, as well
as changes to the device tree source files to add support for those
devices, and a couple of new boards, most notably Samsung's Exynos5
based Chromebook.
The changes depend on earlier platform specific updates and touch
the
This is the third and smallest of the SoC specific updates.
Changes include:
* SMP support for the Xilinx zynq platform
* Smaller imx changes
* LPAE support for mvebu
* Moving the orion5x, kirkwood, dove and mvebu platforms
to a common "mbus" driver for their internal devices.
It would be good
These continue the multiplatform support for exynos, adding support
for building most of the essential drivers (clocksource, clk, irqchip)
when combined with other platforms. As a result, it should become
really easy to add full multiplatform exynos support in 3.11, although
we don't yet enable it
These are cleanups and smaller changes that either depend on earlier
feature branches or came in late during the development cycle.
We normally try to get all cleanups early, so these are the exceptions:
- A follow-up on the clocksource reworks, hopefully the last time
we need to merge
On 05/06/2013 11:53 PM, Ingo Molnar wrote:
* Feng Tang wrote:
is even worse than that. Machine can stay is s2ram for weeks (for a
lot more if it is desktop and you do s2ram for powersaving). Also
temperature of CPU varies a lot between active and s2ram states. Is
TSC good enough?
Yes, I
On 05/07/2013 08:58 AM, Syed Salman Mansoor wrote:
> Fix checkpatch.pl warnings in a20.c
> i) WARNING: please, no spaces at the start of a line
> ii) WARNING: suspect code indent for conditional statements
> iii) ERROR: trailing whitespace
This patch doesn't actually change anything meaningful.
May 7, 2013 09:25:40 PM,Bjorn Helgaas wrote:
> [+cc Phillip]
>
>> I would suspect that Windows' complaint about the BIOS mucking up the MTRRs
>> is likely the best hint. Likely Windows is detecting the problem and fixing
>> it up on resume, thus it only complains about "reduced resume
On 7 May 2013 16:52, Christopher Covington wrote:
> On 05/07/2013 08:19 AM, Peter Maydell wrote:
>> Well, at the moment EARLY_PRINTK is hardcoded to
>> "use some specific UART or equivalent selected at
>> compile time". So the equivalent presumably would
>> be to hard-compile "use
Fix checkpatch.pl warnings in a20.c
i) WARNING: please, no spaces at the start of a line
ii) WARNING: suspect code indent for conditional statements
iii) ERROR: trailing whitespace
Signed-off-by: Syed Salman Mansoor
---
arch/x86/boot/a20.c | 48
Thanks a lot.
I am trying again. Hopefully this will work :)
On Tue, May 7, 2013 at 6:50 PM, Borislav Petkov wrote:
> On Tue, May 07, 2013 at 06:20:22PM +0500, Syed Salman Mansoor wrote:
>> Signed-off-by: Syed Salman Mansoor
>
> No,
>
> this is still wrong:
>
> Subject: [PATCH] x86, setup:
On Tue, May 07, 2013 at 05:24:57PM +0200, Thomas Gleixner wrote:
>
>
> On Tue, 7 May 2013, Mel Gorman wrote:
>
> > On Tue, May 07, 2013 at 08:23:48PM +0800, Zhang Yi wrote:
> > > diff -uprN linux3.9-orig/kernel/futex.c linux3.9/kernel/futex.c
> > > --- linux3.9-orig/kernel/futex.c 2013-04-15
On 05/07/2013 08:19 AM, Peter Maydell wrote:
> On 7 May 2013 05:46, Rusty Russell wrote:
>> Peter Maydell writes:
>>> That all looks like sensible QEMU implementation possibilities
>>> but it seems to be a bit of a non-sequitur from "how do we
>>> tell the kernel to actually use this?"
>>
>> You
On 05/07/2013 05:08 AM, Will Deacon wrote:
> On Mon, May 06, 2013 at 07:01:23PM +0100, Christopher Covington wrote:
>> Hi Will,
>>
>> On 05/03/2013 01:35 PM, Will Deacon wrote:
>>> Hi all,
>>>
>>> This small patch set may look a little over a month late, but there is a
>>> serious reason for
On Tue, 7 May 2013, Pekka Enberg wrote:
> On Tue, May 7, 2013 at 5:23 PM, Christoph Lameter wrote:
> > Well this is because you did not take the patch that changed the way
> > KMALLOC_SHIFT_HIGH is treated.
>
> Is that still needed? I only took the ones Tetsuo said were needed to
> fix the issue
On Tue, May 7, 2013 at 4:39 AM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return a negative error code from the error handling
> case instead of 0, as done elsewhere in this function.
>
> Signed-off-by: Wei Yongjun
Good catch, thanks!
Acked-by: Kees Cook
-Kees
--
Kees Cook
Chrome
On Tue, May 07, 2013 at 10:20:30AM +0800, Gao feng wrote:
> diff --git a/include/linux/audit.h b/include/linux/audit.h
> index 684599b..33e6584 100644
> --- a/include/linux/audit.h
> +++ b/include/linux/audit.h
> @@ -441,7 +441,8 @@ extern int audit_filter_type(int type);
> extern int
201 - 300 of 1340 matches
Mail list logo
