From: Greg KH <gregkh@linuxfoundation.org>
To: pramod gurav <pramod.gurav.etc@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Driver core fixes for 3.16-rc4
Date: Fri, 4 Jul 2014 10:40:51 -0700 [thread overview]
Message-ID: <20140704174051.GE25992@kroah.com> (raw)
In-Reply-To: <CAMf-jSnFqUcyCNOa-UecW3SwmVr45Nvo2Qj3DKDu2-CnPgv2pw@mail.gmail.com>
On Fri, Jul 04, 2014 at 11:52:16AM +0530, pramod gurav wrote:
> On Fri, Jul 4, 2014 at 6:30 AM, Greg KH <gregkh@linuxfoundation.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).
It all depends on the maintainers of those drivers / files, please
discuss it with them, I have no control over that.
best of luck,
greg k-h
prev parent reply other threads:[~2014-07-04 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 1:00 [GIT PULL] Driver core fixes for 3.16-rc4 Greg KH
2014-07-04 6:22 ` pramod gurav
2014-07-04 17:40 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140704174051.GE25992@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pramod.gurav.etc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.