From: Greg KH <gregkh@linuxfoundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: Need Clarification about Whether i can change some Specific Staging Code
Date: Sun, 13 Apr 2014 04:43:17 +0000 [thread overview]
Message-ID: <20140413044317.GA15698@kroah.com> (raw)
In-Reply-To: <534A0341.1050303@gmail.com>
On Sun, Apr 13, 2014 at 08:53:45AM +0530, Kumar Gaurav wrote:
> Hi Greg,
>
> I was checking drivers code to see which are still using semaphore. I
> found some in staging. When i opened the code for upgrading that to
> MUTEX i found a note. that says:
>
> * NOTE TO LINUX KERNEL HACKERS: DO NOT REFORMAT THIS CODE!
> *
> * This is shared code between Digi's CVS archive and the
> * Linux Kernel sources.
> * Changing the source just for reformatting needlessly breaks
> * our CVS diff history.
> *
> * Send any bug fixes/changes to: Eng.Linux at digi dot com.
> * Thank you.
> */
>
> Involved codes are
> ./drivers/staging/dgap/dgap_tty.c
> ./drivers/staging/dgnc/dgnc_tty.c
>
> Please let me know if i can submit a patch against these files.
Yes you can, in fact, you can send a patch to remove those lines :)
greg k-h
prev parent reply other threads:[~2014-04-13 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 3:35 Need Clarification about Whether i can change some Specific Staging Code Kumar Gaurav
2014-04-13 4:43 ` 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=20140413044317.GA15698@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox