Good Day,
I am Matthias Pilz, I work with a security/courier company based in Turkey. I’m
the scan specialist who head the scan department, my job description is to scan
all consignment to ensure that it complies with risk assessment, In the course
of my duty from the assessment of my scan repor
Good Day
I am James Mcgregor,my principal’s wish, to make huge financial investment in
your home country .
Please, I will provide more details about the transaction if you are sure you
can handle classified information and also let me know your entitlement for the
solicited role,
I shall be expe
Good Day
I am Ho-Seok Yang,my principal’s wish, to make huge financial investment in
your home country Please, I will provide more details about the transaction if
you are sure you can handle classified information and also let me know your
entitlement for the solicited role
I shall be expecting
Good Day
I am Ho-Seok Yang, Pleasant greetings to you as i seek your indulgence to
introduce to you the desire of my principal’s wish, to make huge financial
investment in your home country on areas of oil and gas, real estate, tourism
and hotel, manufacturing and production company, agricultur
Good day,
You have been selected to receive my grant donation. Please, contact me for
further detail.to email mrsveraael...@gmail.com
Best Regards,
Mrs. Vera Aellen.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproje
Good day,
You have been selected to receive my grant donation. Please, contact me for
further detail.to email mrsveraael...@gmail.com
Best Regards,
Mrs. Vera Aellen.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproje
Good day,
You have been selected to receive my grant donation. Please, contact me for
further detail.reply to mrsveraael...@gmail.com
Best Regards,
Mrs. Vera Aellen.
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverprojec
On Tue, Sep 11, 2018 at 10:20:41AM +0300, Dan Carpenter wrote:
> On Tue, Sep 11, 2018 at 06:48:27AM +, Nicholas Mc Guire wrote:
> > On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
> > > Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
> > > drm_dev_register.") repla
On Tue, Sep 11, 2018 at 07:41:10AM +, Nicholas Mc Guire wrote:
> On Tue, Sep 11, 2018 at 08:53:35AM +0200, Hans de Goede wrote:
> > Hi,
> >
> > On 11-09-18 08:48, Nicholas Mc Guire wrote:
> > >On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
> > >>Commit 1daddbc8dec5 ("staging: v
On Tue, Sep 11, 2018 at 08:53:35AM +0200, Hans de Goede wrote:
> Hi,
>
> On 11-09-18 08:48, Nicholas Mc Guire wrote:
> >On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
> >>Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
> >>drm_dev_register.") replaced the obsolere dr
On Tue, Sep 11, 2018 at 06:48:27AM +, Nicholas Mc Guire wrote:
> On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
> > Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
> > drm_dev_register.") replaced the obsolere drm_get_pci_dev() with
> > normal pci probe and remove
On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
> Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
> drm_dev_register.") replaced the obsolere drm_get_pci_dev() with
> normal pci probe and remove functions.
>
> But the new vbox_pci_probe() is missing a pci_enable_devic
Hi,
On 11-09-18 08:48, Nicholas Mc Guire wrote:
On Mon, Sep 10, 2018 at 08:30:38PM +0200, Hans de Goede wrote:
Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
drm_dev_register.") replaced the obsolere drm_get_pci_dev() with
normal pci probe and remove functions.
But the new vbox
Commit 1daddbc8dec5 ("staging: vboxvideo: Update driver to use
drm_dev_register.") replaced the obsolere drm_get_pci_dev() with
normal pci probe and remove functions.
But the new vbox_pci_probe() is missing a pci_enable_device() call,
causing interrupts to not be delivered. This causes resizes of
On 12/11/16 18:19, Brian Masney wrote:
> in_illuminance_calibrate_store() did not check to see if the chip is
> in a working state. This patch adds the proper check. The return value
> from taos_als_calibrate() was also not checked in this function, so the
> proper check was also
in_illuminance_calibrate_store() did not check to see if the chip is
in a working state. This patch adds the proper check. The return value
from taos_als_calibrate() was also not checked in this function, so the
proper check was also added while changes are being made here.
Signed-off-by: Brian
After clock_start() removal from from soc_camera_probe() (commit
9aea470b39 '[media] soc-camera: switch I2C subdevice drivers to use
v4l2-clk', introduced in v3.11), it occurred omap1_camera's sensor
can't be probed successfully without its clock being turned on in
advance. Fix that by surrounding
Hi All,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving gs_fpgaboot out of staging
in over a year. Are there any plans to clean it up and move it out soon?
Or it should be deleted?
Thanks,
Ksenija
r. I had discuss early with
> Mike Shuey since he
>
> was also working in that area but will be migrating to the lustre core.
>
>
>
> Since more people are getting involved we need to find a way to break
> up the work to avoid
>
> duplicate work. Should the work be br
On Thursday, May 21, 2015 12:57:40 PM Xose Vazquez Perez wrote:
> On 05/07/2015 12:37 AM, Jes Sorensen wrote:
>
> > Christian Lamparter writes:
>
> >> But as I mentioned before: "I would recommend adding just a _friendly_
> >> printk"
>
> > I'm happy adding a printk - what would you like it to
On 05/07/2015 12:37 AM, Jes Sorensen wrote:
> Christian Lamparter writes:
>> But as I mentioned before: "I would recommend adding just a _friendly_
>> printk"
> I'm happy adding a printk - what would you like it to say?
Christian, ping!
BTW, why rtl8192su is not inside the kernel yet?
Is ther
Christian Lamparter writes:
> On Tue, May 5, 2015 at 7:23 PM, Jes Sorensen wrote:
>> Xose Vazquez Perez writes:
>>> On 06/20/2014 10:52 PM, Christian Lamparter wrote:
>>>
rtl8192su development is chugging along. It just doesn't take place on
driverdev list. The driver reached "feature
On Tue, May 5, 2015 at 7:23 PM, Jes Sorensen wrote:
> Xose Vazquez Perez writes:
>> On 06/20/2014 10:52 PM, Christian Lamparter wrote:
>>
>>> rtl8192su development is chugging along. It just doesn't take place on
>>> driverdev list. The driver reached "feature parity" with rtl8192cu for
>>> some
Xose Vazquez Perez writes:
> On 06/20/2014 10:52 PM, Christian Lamparter wrote:
>
>> rtl8192su development is chugging along. It just doesn't take place on
>> driverdev list. The driver reached "feature parity" with rtl8192cu for
>> some time ago. But as with rtl8192cu, I would recommend adding ju
On 06/20/2014 10:52 PM, Christian Lamparter wrote:
> rtl8192su development is chugging along. It just doesn't take place on
> driverdev list. The driver reached "feature parity" with rtl8192cu for
> some time ago. But as with rtl8192cu, I would recommend adding just
> a friendly "printk". Yup, Rea
On Mon, Jun 30, 2014 at 10:39:33AM +0200, Laurent Navet wrote:
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed
> > that
> > nobody seems to have worked towards moving line6 out of staging in over
> > a year. Are there any plans to clean it up and move it out
ep out of staging in over
> > > > > a
> > > > > year. Are there any plans to clean it up and move it out soon?
> > > >
> > > > No response from Mark here.
> > > >
> > > > Alan, Jayant, either of you know what the status of the sep s
No response from Mark here.
> > >
> > > Alan, Jayant, either of you know what the status of the sep staging
> > > driver is?
> >
> > I believe "works last time anyone checked". I don't think we have anyone
> > officially working on
f the sep staging
> > driver is?
>
> I believe "works last time anyone checked". I don't think we have anyone
> officially working on the early Intel phone cpus for upstream any more.
So can we just drop it then? If no one is working on moving it out o
ng in over a
> > year. Are there any plans to clean it up and move it out soon?
>
> No response from Mark here.
>
> Alan, Jayant, either of you know what the status of the sep staging
> driver is?
I believe "works last time anyone checked". I don't think
On 23/06/14 23:32, Kristina Martšenko wrote:
> Hi Mark,
>
> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> nobody seems to have worked towards moving sep out of staging in over a
> year. Are there any plans to clean it up and move it out soon?
No response from Mark her
From: Jyri Sarha
This code is not working currently and it can be removed. There is a
conflict in sharing resources with the actual HDMI driver and with
the ASoC HDMI audio DAI driver.
Signed-off-by: Jyri Sarha
Signed-off-by: Tony Lindgren
Signed-off-by: sam-the-6
---
arch/arm/mach-omap2
t;>>>
>>>>>>> thanks for the notice. Please, give me some time for
>>>>>>> checking here how we want to go forward with this.
>>>>>>
>>>>>> What do you mean by this? You all have had a lot of time,
>>
them previously? What is preventing you to send
them?
Because it's only for a few weeks that I've been working on them.
They basically convert all "camelCase" and "Hungarian notation" names to
Linux convention and fix some checkpatch errors (no logic is modified).
>>>thanks for the notice. Please, give me some time for checking here how
> >>>>we want to go forward with this.
> >>>
> >>>What do you mean by this? You all have had a lot of time, with no real
> >>>progress at all? How about we delete the dr
On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
>
>
> On 9.07.2014 10:07, Tony Lindgren wrote:
> >* Suman Anna [140708 11:40]:
> >>Hi Peter,
> >>
> >>On 07/08/2014 09:36 AM, Greg KH wrote:
> >>>On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
> Hello,
>
On Thu, Jul 10, 2014 at 12:11 PM, Greg KH wrote:
>
> On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
> >
> >
> > On 9.07.2014 10:07, Tony Lindgren wrote:
> > >* Suman Anna [140708 11:40]:
> > >>Hi Peter,
> > >>
> > >>On 07/08/2014 09:36 AM, Greg KH wrote:
> > >>>On Tue, Jul 08,
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done
* Suman Anna [140708 11:40]:
> Hi Peter,
>
> On 07/08/2014 09:36 AM, Greg KH wrote:
> > On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
> >> Hello,
> >>
> Given the total lack of response here, I suggest just deleting the
> driver. No one has ever done the "real work" t
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
> On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
>> Hello,
>>
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the "real work" that is going to be
required to get this c
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
> Hello,
>
> > > Given the total lack of response here, I suggest just deleting the
> > > driver. No one has ever done the "real work" that is going to be
> > > required to get this code out of staging. It has had build errors
> > >
Hello,
> > Given the total lack of response here, I suggest just deleting the
> > driver. No one has ever done the "real work" that is going to be
> > required to get this code out of staging. It has had build errors
> > causing it to not even be usable for some kernel versions with no one
> > n
On 29/06/14 19:42, Greg KH wrote:
> On Fri, Jun 20, 2014 at 07:05:17PM +0300, Kristina Martšenko wrote:
>> On 20/06/14 18:43, Kristina Martšenko wrote:
>>> Hi Omar,
>>>
>>> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
>>> nobody seems to have worked towards moving tidspb
On 07/01/2014 09:17 PM, Michalis Pappas wrote:
> The wimax.h interface specifies communication through "message pipes", a
> means of free-form communication between user-space and the driver. So
> my understanding is that the library only needs to replace the lowest
> layer (ie ioctl/netlink) with
On 07/01/2014 07:38 PM, Olof Johansson wrote:
> I'm not Greg, but in general the requirements of not breaking the
> userspace ABI does not apply to staging drivers.
>
> However, that doesn't mean that it makes sense to gratuitously break it
> "just because".
Certainly not. My only concern was ab
On 07/01/2014 07:29 PM, Ben Chan wrote:
>
> [Ben] AFAIK, there is another Intel i2400m WiMAX driver in kernel. The
> wimax-tools probably works with that particular driver. I haven't
> looked at either the i2400m driver or wimax-tools, and need to spend
> some time to figure out the differences be
the FSM was implemented, and even that is actually broken.
>>
>> I put together a patch that removes the old interface and I am currently
>> working on replacing it with the one defined in net/wimax.h.
>> We'll probably need to do some testing on the actual ha
On Tue, Jul 1, 2014 at 9:22 AM, Michalis Pappas wrote:
>
> Hmm, I wasn't aware of the existence of the user-space library. From a
> peek through the sources I notice some copyright disclaimers by GCT. How
> do they distribute that library? Who is the maintainer?
[Ben] The user-space library in Ch
ation was only partially complete. Only a minor fraction
> of the FSM was implemented, and even that is actually broken.
>
> I put together a patch that removes the old interface and I am currently
> working on replacing it with the one defined in net/wimax.h.
>
be using netlink generic).
- Uses a custom netlink event notification mechanism (should be using
the one defined in net/wimax.h).
- The implementation was only partially complete. Only a minor fraction
of the FSM was implemented, and even that is actually broken.
I put together a patch that removes the
On 24/06/14 15:44, Bob Beers wrote:
> No,I am not able to work on that. It probably should be removed.
> Bob
Okay then. No one else has shown interest in it either in the past week,
so I'll go ahead and remove it.
Thanks,
Kristina
___
devel mailing list
Looks like there is a broken link on
http://www.mail-archive.com/i-kan-icw@xc.org/msg00023.html to
http://www.pslgroup.com/DOCGUIDE.HTM. You might also want to add some of these
resources I found useful...
http://online.annamaria.edu/resource/business-and-leadership/health-informatics-qualified
> I'm helping Greg do a bit of cleanup in the staging tree. I noticed
> that
> nobody seems to have worked towards moving line6 out of staging in over
> a year. Are there any plans to clean it up and move it out soon?
> Because
> otherwise we're going to have to delete the d
in mind if it turns out that no one else is working on it).
>
> Thanks,
>
> Michalis
>
Hi Michalis,
Thanks for your help. I'm happy to collaborate if you're interested
too. I'm not the author of the driver, so my knowledge is limited to
what I've read from the
On Fri, Jun 20, 2014 at 07:05:17PM +0300, Kristina Martšenko wrote:
> On 20/06/14 18:43, Kristina Martšenko wrote:
> > Hi Omar,
> >
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving tidspbridge out of staging in
> > over a y
On 06/28/2014 07:39 AM, Ben Chan wrote:
> On Wed, Jun 25, 2014 at 5:11 AM, Michalis Pappas wrote:
>>
>>
>> Hi everyone,
>>
>> I've been working on a driver review for gdm72xx and I think there are some
>> more issues to be fixed except from stuff rep
On Wed, Jun 25, 2014 at 5:11 AM, Michalis Pappas wrote:
>
>
> Hi everyone,
>
> I've been working on a driver review for gdm72xx and I think there are some
> more issues to be fixed except from stuff reported by checkpatch.pl. Here's
> what I've come up wit
Am 24.06.2014 16:12, schrieb Stefan Hajnoczi:
On Tue, Jun 24, 2014 at 9:52 PM, Greg KH wrote:
On Tue, Jun 24, 2014 at 11:54:10AM +0800, Stefan Hajnoczi wrote:
On Tue, Jun 24, 2014 at 4:23 AM, Kristina Martšenko
wrote:
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
n
iver and if you decide to
continue to work on it, we can revert that deletion and go from there?
thanks,
greg k-h
Hi,
I have a hundred patches for this driver ready to send.
Why have you not sent them previously? What is preventing you to send
them?
Because it's only for a few weeks th
On Fri, Jun 27, 2014 at 03:04:43PM +0200, Luca Ellero wrote:
> Il 26/06/2014 21:23, Greg KH ha scritto:
> >On Thu, Jun 26, 2014 at 09:36:17AM +0200, Alois Schloegl wrote:
> >>On 2014-06-18 13:33, Kristina Martšenko wrote:
> >>>Hi Alois,
> >>>
> >>>I'm helping Greg do a bit of cleanup in the staging
Il 26/06/2014 21:23, Greg KH ha scritto:
On Thu, Jun 26, 2014 at 09:36:17AM +0200, Alois Schloegl wrote:
On 2014-06-18 13:33, Kristina Martšenko wrote:
Hi Alois,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving ced1401 out of s
On Fri, Jun 27, 2014 at 1:39 AM, Greg KH wrote:
> On Tue, Jun 24, 2014 at 10:12:03PM +0800, Stefan Hajnoczi wrote:
>> On Tue, Jun 24, 2014 at 9:52 PM, Greg KH wrote:
>> > On Tue, Jun 24, 2014 at 11:54:10AM +0800, Stefan Hajnoczi wrote:
>> >> On Tue, Jun 24, 2014 at 4:23 AM, Kristina Martšenko
>>
On Tue, Jun 24, 2014 at 10:12:03PM +0800, Stefan Hajnoczi wrote:
> On Tue, Jun 24, 2014 at 9:52 PM, Greg KH wrote:
> > On Tue, Jun 24, 2014 at 11:54:10AM +0800, Stefan Hajnoczi wrote:
> >> On Tue, Jun 24, 2014 at 4:23 AM, Kristina Martšenko
> >> wrote:
> >> > I'm helping Greg do a bit of cleanup
On Thu, Jun 26, 2014 at 09:36:17AM +0200, Alois Schloegl wrote:
> On 2014-06-18 13:33, Kristina Martšenko wrote:
> > Hi Alois,
> >
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving ced1401 out of staging in
> > over a year.
On 2014-06-18 13:33, Kristina Martšenko wrote:
> Hi Alois,
>
> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> nobody seems to have worked towards moving ced1401 out of staging in
> over a year. Are there any plans to clean it up and move it out soon?
> Because otherwise
ht?
>
Hi everyone,
I've been working on a driver review for gdm72xx and I think there are some
more issues to be fixed except from stuff reported by checkpatch.pl. Here's
what I've come up with so far:
First of all, during a patch review, Dan Carpenter (cced) mentioned some
On Tue, Jun 24, 2014 at 9:52 PM, Greg KH wrote:
> On Tue, Jun 24, 2014 at 11:54:10AM +0800, Stefan Hajnoczi wrote:
>> On Tue, Jun 24, 2014 at 4:23 AM, Kristina Martšenko
>> wrote:
>> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
>> > nobody seems to have worked toward
On Tue, Jun 24, 2014 at 11:54:10AM +0800, Stefan Hajnoczi wrote:
> On Tue, Jun 24, 2014 at 4:23 AM, Kristina Martšenko
> wrote:
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving line6 out of staging in over
> > a year. Are t
On Tue, Jun 24, 2014 at 11:14:40AM +0200, Luca Ellero wrote:
> On 23/06/2014 22:19, Kristina Martšenko wrote:> Hi Angelo,
> >
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving quickstart out of staging in
> > over a year. Are
On Tue, Jun 24, 2014 at 12:12:55AM -0700, Ben Chan wrote:
> On Mon, Jun 23, 2014 at 2:33 PM, Kristina Martšenko
> wrote:
> >
> > Here is an example of another driver being moved out:
> > http://www.spinics.net/lists/linux-usb/msg100924.html
> >
>
> Thanks Kristina. checkpatch reports 1 errors an
On 23/06/2014 22:19, Kristina Martšenko wrote:> Hi Angelo,
>
> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> nobody seems to have worked towards moving quickstart out of staging in
> over a year. Are there any plans to clean it up and move it out soon?
> Because otherw
On Mon, Jun 23, 2014 at 2:33 PM, Kristina Martšenko
wrote:
>
> Here is an example of another driver being moved out:
> http://www.spinics.net/lists/linux-usb/msg100924.html
>
Thanks Kristina. checkpatch reports 1 errors and 17 warnings on the
current driver.
I guess I need to first submit patch
On Tue, Jun 24, 2014 at 4:23 AM, Kristina Martšenko
wrote:
> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> nobody seems to have worked towards moving line6 out of staging in over
> a year. Are there any plans to clean it up and move it out soon? Because
> otherwise we'
staging in over a year. Are there any plans to clean these drivers up
>> and move them out soon? Because otherwise we're going to have to delete
>> them, as we don't want staging to become a permanent place for
>> unfinished code.
>>
>> Thanks,
>> Kri
. He is actively reworking it with tens of patches per
> week, but he has not yet tackled the conversion to mac80211. It should
> have much in common with the RTL8723AE, but it will still be a big job.
>
> The PCI group recently sent me new code for all the PCI devices, and I
> am
er reached "feature parity" with rtl8192cu for
>>> some time ago.
>>
>> Great, thanks for letting me know. If you plan to keep working on it, do
>> you think it would be a good idea to add yourself and a link to your
>> github to the staging driver'
soon? Because otherwise we're going to have to delete
them, as we don't want staging to become a permanent place for
unfinished code.
Thanks,
Kristina
In the case of serqt_usb2, I'm certainly not going to be working on it.
If I had a multi-port version of one of those devices, I&
On 23/06/14 23:41, Ben Chan wrote:
> Hi Kristina and Greg,
>
> I can help migrate the gdm72xx driver from staging to mainline. I
> believe the issues in TODO have been addressed.
That's great, thanks!
> Is there a migration process that I should follow?
I don't think there's anything special yo
Hi Mark,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving sep out of staging in over a
year. Are there any plans to clean it up and move it out soon? Because
otherwise we're going to have to delete the driver, as we don't want
stag
Hi Bill,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving dgrp or serqt_usb2 out of
staging in over a year. Are there any plans to clean these drivers up
and move them out soon? Because otherwise we're going to have to delete
them,
Hi Evan,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving phison out of staging in over
a year. Are there any plans to clean it up and move it out soon? Because
otherwise we're going to have to delete the driver, as we don't want
s
Hi Markus,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving line6 out of staging in over
a year. Are there any plans to clean it up and move it out soon? Because
otherwise we're going to have to delete the driver, as we don't want
Hi Daniel,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving silicom out of staging in
over a year. Are there any plans to clean it up and move it out soon?
Because otherwise we're going to have to delete the driver, as we don't
wan
Hi Angelo,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving quickstart out of staging in
over a year. Are there any plans to clean it up and move it out soon?
Because otherwise we're going to have to delete the driver, as we don't
Hi Sage,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving gdm72xx out of staging in
over a year. Are there any plans to clean it up and move it out soon?
Because otherwise we're going to have to delete the driver, as we don't
want
Hi Bob,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving cxt1e1 out of staging in over
a year. Are there any plans to clean it up and move it out soon? Because
otherwise we're going to have to delete the driver, as we don't want
st
r, as we don't
> >>> want staging to become a permanent place for unfinished code.
> >> Hi Kristina,
> >>
> >> I'm not working on anything for wlags49_h2.
> >
> > Great, no objection if we delete it?
>
> Henk also sent the followin
ards moving wlags49_h2(5) out of staging
>>> in over a year. Are there any plans to clean it up and move it out soon?
>>> Because otherwise we're going to have to delete the driver, as we don't
>>> want staging to become a permanent place for unfinished code.
>>
On Sat, Jun 21, 2014 at 08:03:25PM +0200, Pavel Machek wrote:
> On Fri 2014-06-20 18:45:08, Kristina Martšenko wrote:
> > Hi Pavel,
> >
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving winbond out of staging in
> > over a y
over a year. Are there any plans to clean it up and move it out soon?
> >Because otherwise we're going to have to delete the driver, as we don't
> >want staging to become a permanent place for unfinished code.
> Hi Kristina,
>
> I'm not working on anything for wlags4
unfinished code.
Christian Lamparter is working on a new driver
based on mac80211: https://github.com/chunkeey/rtl8192su
Thanks for pointing that out and forwarding the email to Christian.
rtl8192su development is chugging along. It just doesn't take place on
driverdev list. The driver rea
On Fri 2014-06-20 18:45:08, Kristina Martšenko wrote:
> Hi Pavel,
>
> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> nobody seems to have worked towards moving winbond out of staging in
> over a year. Are there any plans to clean it up and move it out soon?
Plans, yes,
't
> >>> want staging to become a permanent place for unfinished code.
> >> Christian Lamparter is working on a new driver
> >> based on mac80211: https://github.com/chunkeey/rtl8192su
>
> Thanks for pointing that out and forwarding the email to Christian.
7;re going to have to delete the driver, as we don't
want staging to become a permanent place for unfinished code.
Hi Kristina,
I'm not working on anything for wlags49_h2.
Thanks for asking,
Dave.
___
devel mailing list
de...@linuxdr
clean up their driver if they can just
put it in staging and it will stay there forever? We end up with a
larger and larger body of code in the kernel that's low quality, and
that means more bugs etc. And that's not good for anyone, including the
users.
In this case, since Christian is worki
8712 out of staging in
>>> over a year. Are there any plans to clean it up and move it out soon?
>>> Because otherwise we're going to have to delete the driver, as we don't
>>> want staging to become a permanent place for unfinished code.
>> Christi
year. Are there any plans to clean it up and move it out soon?
> > > > Because
> > > > > otherwise we're going to have to delete the driver, as we don't
> > > > want
> > > > > staging to become a permanent place for unfinished code
ns to clean it up and move it out soon?
> > Because otherwise we're going to have to delete the driver, as we don't
> > want staging to become a permanent place for unfinished code.
> Christian Lamparter is working on a new driver
> based on mac80211: https://github.
On Fri, Jun 20, 2014 at 10:13:27AM -0700, Stephen Hemminger wrote:
> On Fri, 20 Jun 2014 19:49:33 +0300
> Kristina Martšenko wrote:
>
> > Hi Stephen,
> >
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving bcm out of staging
x27;re going to have to delete the driver, as we don't want
> > > > staging to become a permanent place for unfinished code.
> > > >
> > > > Thanks,
> > > > Kristina
> > >
> > >
> > >
> > > Hi Kristina,
> &
1 - 100 of 144 matches
Mail list logo
