[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMf-jSnFqUcyCNOa-UecW3SwmVr45Nvo2Qj3DKDu2-CnPgv2pw@mail.gmail.com>
Date: Fri, 4 Jul 2014 11:52:16 +0530
From: pramod gurav <pramod.gurav.etc@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Driver core fixes for 3.16-rc4
On Fri, Jul 4, 2014 at 6:30 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> The following changes since commit 4c834452aad01531db949414f94f817a86348d59:
>
> Linux 3.16-rc3 (2014-06-29 14:11:36 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-3.16-rc4
>
> for you to fetch changes up to 4a3a99045177369700c60d074c0e525e8093b0fc:
>
> lz4: add overrun checks to lz4_uncompress_unknownoutputsize() (2014-07-03 16:12:04 -0700)
>
> ----------------------------------------------------------------
> Driver core fixes for 3.16-rc4
Hi Greg,
What should I do if I come across some coding guidelines issues,
compile warning in some core drivers like fs/, cpuidle etc?
For exa: A fix in CPUIdle
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg668109.html
Shall I continue sending the corrections? Will they be accepted at
this point of time? Because I saw no response as a lot of code was
being added to these drivers (read cpuidle).
--
Thanks and Regards
Pramod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists