From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [PATCH v4] Staging: media: vino: Replace printk() and dprintk() with dev_dbg()
Date: Fri, 20 Feb 2015 16:31:00 +0530 [thread overview]
Message-ID: <54E713EC.7050003@linux.vnet.ibm.com> (raw)
In-Reply-To: <96fe9c8a-4cb6-4058-a4be-3740e3e3cf58@googlegroups.com>
Hi Ksenija
On 02/20/2015 03:09 PM, Ksenija Stanojevic wrote:
> Hm, so I should not send this patch at all?
Yes, please avoid it as it will not make it to mainline.
Regards
Preeti U Murthy
>
> On Friday, February 20, 2015 at 10:34:55 AM UTC+1, Arnd Bergmann wrote:
>
> On Friday 20 February 2015 10:21:48 Ksenija Stanojević wrote:
> > I based it on staging-next, like in a tutorial
>
> Ok, I've investigated a bit further now and found that four
> staging drivers have been removed in mainline that are still
> present in staging-next:
>
> drivers/staging/line6/ (moved to sound/usb)
> drivers/staging/media/parport/
> drivers/staging/media/tlg2300/
> drivers/staging/media/vino/
>
> Any patches against these could in theory still make it into
> Greg's tree but they would be completely pointless because they
> get removed with the next mainline synchronization.
>
> Arnd
>
> --
> You received this message because you are subscribed to the Google
> Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to outreachy-kernel+unsubscribe@googlegroups.com
> <mailto:outreachy-kernel+unsubscribe@googlegroups.com>.
> To post to this group, send email to outreachy-kernel@googlegroups.com
> <mailto:outreachy-kernel@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/outreachy-kernel/96fe9c8a-4cb6-4058-a4be-3740e3e3cf58%40googlegroups.com
> <https://groups.google.com/d/msgid/outreachy-kernel/96fe9c8a-4cb6-4058-a4be-3740e3e3cf58%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2015-02-20 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 18:04 [PATCH v4] Staging: media: vino: Replace printk() and dprintk() with dev_dbg() Ksenija Stanojevic
2015-02-19 18:11 ` Ksenija Stanojevic
2015-02-20 9:15 ` [Outreachy kernel] " Arnd Bergmann
2015-02-20 9:21 ` Ksenija Stanojević
2015-02-20 9:34 ` Arnd Bergmann
2015-02-20 9:39 ` Ksenija Stanojevic
2015-02-20 11:01 ` Preeti U Murthy [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=54E713EC.7050003@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksenija.stanojevic@gmail.com \
--cc=outreachy-kernel@googlegroups.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.