Re: Get Back Into Kernel Work
On Sun, Mar 15, 2015 at 12:24:12PM -0400, Ruben Safir wrote: > On Sun, Mar 15, 2015 at 05:16:27PM +0100, Levente Kurusa wrote: > > On Sun, Mar 15, 2015 at 12:01:27PM -0400, Nicholas Krause wrote: > > > >> [...] > > > I was interested in Socs in staging as I believe there are a few > > > would someone like to point me to one that I can get hardware for. > > > > Please read my message again. It should be YOU who does the research > > about the work that YOU want to do, not us... > > > I didn't write this. Are you intentionally trolling this? Nobody's claiming you did. This is a different thread to yours, with a different subject line. Note that none of the quoted messages above had your name as attribution. > The initial message under this subject had nothing to do with this. > BTW - the atitiude is piss poor for what is SUPPOSED to be newbies area. > Try taking some trips from Ernie and Fewer from Bert. This particular newbie (nick) has a reasonably long and ignoble history in the kernel development area. He used up quite a lot of the available polite late last summer, and isn't at the moment giving any indications that he's made any improvements. > PS - no need to CC me when I'm reading the list. It's the default position on these mailing lists. You're generally not going to have anyone remember that you don't want to be CC'd. A message in your .sig to that effect might help, but it probably won't. Hugo. -- Hugo Mills | Be pure. hugo@... carfax.org.uk | Be vigilant. http://carfax.org.uk/ | Behave. PGP: 65E74AC0 | Torquemada, Nemesis signature.asc Description: Digital signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: [PATCH] staging: Fix spacing between function name and parentheses
On Sat, Oct 11, 2014 at 09:44:05AM -0400, nick wrote:
> Thank you for your help, I'll study the code and see what I can do
> about it. Do you have any suggestions of how to fix this checkpatch
> warning?
Ignore it. The checker has clearly triggered on a false positive --
this is not a function call, and should not be held to that standard.
(Take a look at where the macro is actually used, to see what's going
on here). Move on to find something more interesting to fix.
Hugo.
> Nick
>
> On 14-10-11 05:53 AM, Kristofer Hallin wrote:
> > Even if you use checkpath you _should_ understand what you are changing.
> > The output of checkpatch merely there to help.
> >
> > In this case you can see that this is a macro just a few lines up in the
> > code.
> > On 11 Oct 2014 11:46, "Sudip Mukherjee" wrote:
> >
> >> I agree. But in my opinion checkpatch is here to help us fix style
> >> problems , but we should not blindly act on checkpatch warnings.
> >>
> >> thanks
> >> sudip
> >>
> >> On Sat, Oct 11, 2014 at 1:57 PM, Peter Senna Tschudin
> >> wrote:
> >>> I think that, in this case, checkpatch.pl contributed:
> >>>
> >>> $ ./scripts/checkpatch.pl -f drivers/staging/octeon-usb/octeon-hcd.c
> >>> WARNING: space prohibited between function name and open parenthesis '('
> >>> #415: FILE: drivers/staging/octeon-usb/octeon-hcd.c:415:
> >>> + if (c.s.field op (value)) {
> >>\
> >>>
> >>>
> >>> On Sat, Oct 11, 2014 at 8:11 AM, Dave Tian
> >> wrote:
> >>>> Agreed - that is why I mentioned the patch is neither right nor useful:)
> >>>>
> >>>> -daveti
> >>>>
> >>>>
> >>>> On Oct 11, 2014, at 2:08 PM, Sudip Mukherjee <
> >> sudipm.mukher...@gmail.com> wrote:
> >>>>
> >>>>> Hi Dave,
> >>>>> It will work. But my point of saying that was c.s.field ==(value) is
> >>>>> again not according to the style.
> >>>>>
> >>>>> thanks
> >>>>> sudip
> >>>>>
> >>>>> On Sat, Oct 11, 2014 at 10:53 AM, Dave Tian
> >> wrote:
> >>>>>> It also works as value is surrounded by (), though I do not think the
> >> patch itself is right or useful.
> >>>>>>
> >>>>>> Dave Tian
> >>>>>> dave.jing.t...@gmail.com
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Oct 11, 2014, at 12:58 PM, Sudip Mukherjee <
> >> sudipm.mukher...@gmail.com> wrote:
> >>>>>>
> >>>>>>> On Fri, Oct 10, 2014 at 09:55:48PM -0400, Nicholas Krause wrote:
> >>>>>>>> Fixes checkpatch coding style warning about unneeded space
> >>>>>>>> between function name an parentheses.
> >>>>>>>>
> >>>>>>>> Signed-off-by: Nicholas Krause
> >>>>>>>> ---
> >>>>>>>> Untested
> >>>>>>>> drivers/staging/octeon-usb/octeon-hcd.c | 2 +-
> >>>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>>>>>
> >>>>>>>> diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
> >> b/drivers/staging/octeon-usb/octeon-hcd.c
> >>>>>>>> index 5f9db4c..bbeb0cc 100644
> >>>>>>>> --- a/drivers/staging/octeon-usb/octeon-hcd.c
> >>>>>>>> +++ b/drivers/staging/octeon-usb/octeon-hcd.c
> >>>>>>>> @@ -412,7 +412,7 @@ struct octeon_hcd {
> >>>>>>>> type c;
> >> \
> >>>>>>>> while (1) {
> >> \
> >>>>>>>> c.u32 = __cvmx_usb_read_csr32(usb, address);
> >> \
> >>>>>>>> -if (c.s.field op (value)) {
> >> \
> >>>>>>>> +if (c.s.field op(value)) {
> >> \
> >>>>>>>
> >>>>>>> have you read the code before modifying it?
> >>>>>>> this is not a function.
> >>>>>>> have you seen how CVMX_WAIT_FOR_FIELD32 is being called?
> >>>>>>> on every call of CVMX_WAIT_FOR_FIELD32 op is the operator "=="
> >>>>>>> so when called the macro will be c.s.field == (value).
> >>>>>>> if your patch is applied then it will become c.s.field ==(value) ..
> >> will that be correct ?
> >>>>>>>
> >>>>>>> thanks
> >>>>>>> sudip
> >>>>>>>
> >>>>>>>> result = 0;
> >> \
> >>>>>>>> break;
> >> \
> >>>>>>>> } else if (cvmx_get_cycle() > done) {
> >> \
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Happiness is mandatory. Are you happy? ---
signature.asc
Description: Digital signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Banned Again
On Mon, Sep 29, 2014 at 06:29:51AM -0400, Nick Krause wrote: > I am getting very annoyed , that I am banned again from my other email > at yoc...@gmail.com are people trying to just prevent me from > being on the list. Is that your goal now? It's not my decision, but my guess is that yes, people are now simply trying to prevent you from being on the kernel mailing lists. Why? Well, after some 3 months or so of people trying their best to help you, giving good advice, and having pretty much all of that advice ignored, you went back to LKML doing the *exact* *same* *thing* that you started out doing. So, three months of concerted effort on behalf of the people trying to help you has been completely lost, from their point of view. At this point, I think you've blown it, probably permanently. You've wasted the goodwill shown to you by others, and there is no more remaining. The only thing you've achieved is to demonstrate that you're a complete waste of anyone else's time, so it's not surprising that nobody's going to listen to you any more. I'm done. Hugo. > Cheers Nick > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- "There's a Martian war machine outside -- they want to talk --- to you about a cure for the common cold." signature.asc Description: Digital signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Issues with Community
On Tue, Sep 16, 2014 at 07:22:15PM -0400, nick wrote: > After numerous tries at good patches and still failing , I am > listening to what you guys stated about my patches check it applies, > grammar and build checks. I am still unable to get a good patch and > would really appreciate it if someone walks me through one good > patch as I will learn this will a tutor and the tutor can help be my > router to the community for now in order to start helping me learn > how to be involved correctly and follow the community rules. I am > willing to work on my patches if someone is willing to do this for > me and help me improve my taste in the communities mouth. Pretty much everybody who's written you an email from these mailing lists in the last two months has been trying to help you in this way. You've consistently ignored (or at least not followed) the advice, which makes the people who gave it feel like it's not worth the effort. Therefore, as it stands, anyone considering helping you will probably think it's a complete waste of time. Phrases such as you've used to date: "I must check things more carefully", "I'm willing to work on my patches", "I will learn this" are no longer good enough: You've used wording like this before, and failed to show that you've learned anything as a result. So, unless you can explain in detail *why* you ignored all the previous advice, *and* you can explain in detail *how* you are modifying your behaviour and working practices so that you can learn from future advice, nobody is likely to want to help you. Go back and read my mail from yesterday. Engage with it -- write your thoughts and explanations on a point-by-point basis. A single three-line response at the end of the mail is not sufficient. If you can't engage with that mail in detail, follow the advice I gave and seek formal assistance for your learning difficulties. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- There are three mistaikes in this sentance. --- signature.asc Description: Digital signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Checkpatch Patches
On Tue, Sep 16, 2014 at 11:44:59AM -0400, Nick Krause wrote: > On Tue, Sep 16, 2014 at 10:19 AM, wrote: > > On Tue, 16 Sep 2014 08:44:27 -0400, nick said: > > > >> I am attaching two check patch patches I wrote in the last few days as I > >> am unable to get a reply > >> from the maintainers. Would someone please send them off for me. > > > > "I am attaching". Fail 3 words in. [snip] > I am going to attach it again and I understand Valdis. I am going to > talk to Sudip about reading and checking > my patches first. The email that you are replying to repeats the statement that attaching the patches is the wrong thing to be doing. And yet, in the reply, you talk about attaching patches. Can you please explain what's going on here? Did you forget about it while you were writing the three line response? Did you simply ignore the words? Did you assume that it didn't apply to you? Did you merely think it wasn't important? Do you have short-term memory problems? Is there something else I don't know about? I understand that you're a student (or will shortly be one), and so far you're showing *major* learning difficulties, without any apparent self-identification of the fact. If you do actually have some kind of learning difficulty, you're going to have to take charge of it yourself, seek professional advice, use that to work out how you can learn, and start doing it, because if you behave like this in any institution of higher learning, you're going to have big problems, probably very quickly. You've spent two months, with *lots* of explicit recommendations on how you should be modifying your behaviour (i.e. learning), and so far you've utterly failed to do so. It's up to you to seek help in identifying the difficulties you have in learning, and to use the results of that to work out how you can do so. This kernel development environment is *absolutely* the wrong one for you to be doing that exercise in. I doubt that there are many (if any) people on this mailing list who have the knowledge or skills to help you. I am certain that if there are any, none of them would be willing to start the process via email. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- "Big data" doesn't just mean increasing the font size --- signature.asc Description: Digital signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Trial Patch
On Wed, Sep 10, 2014 at 07:26:32AM -0400, nick wrote:
> On 14-09-10 12:49 AM, valdis.kletni...@vt.edu wrote:
[snip]
> > Like this one - it's *still* wrong. Because
> >
> > From: Nicholas Krause
> > Date: Tue, 9 Sep 2014 21:12:56 -0400
> >
> > You reposted the same broken patch again.
[snip]
> Here is the correct patch.
> Nick
> >From ad55b627241203a380dd9c708a4feae98446f85f Mon Sep 17 00:00:00 2001
> From: Nicholas Krause
> Date: Tue, 9 Sep 2014 21:12:56 -0400
> Subject: [PATCH] staging: Fix NULL check for allocating the skb in
> r8192E_firmware.c
>
> This patch checks in the loop of the function, fw_download_code if
> a allocated skb is NULL. If the skb is NULL then we first free the
> allocated skbs in the queue of this function with skb_queue_purge
> in order to free the allocated skbs. After the freeing of the queue
> we break out of the do/while of this function as we need to run
> write_nic_byte in order to activate parts of the network card's
> driver.
>
> Signed-off-by: Nicholas Krause
> ---
> drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> index 1a95d1f..a251414 100644
> --- a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> +++ b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> @@ -61,6 +61,10 @@ static bool fw_download_code(struct net_device *dev, u8
> *code_virtual_address,
> }
>
> skb = dev_alloc_skb(frag_length + 4);
> + if (skb == NULL) {
> + skb_queue_purge(&priv->rtllib->skb_waitQ[TXCMD_QUEUE]);
> + break;
> + }
> memcpy((unsigned char *)(skb->cb), &dev, sizeof(dev));
> tcb_desc = (struct cb_desc *)(skb->cb + MAX_DEV_ADDR_SIZE);
> tcb_desc->queue_index = TXCMD_QUEUE;
I'll save Valdis the trouble here. This is still wrong. It's
*identical* to the last one you sent. Bit for bit. Again, you've lost
track of even the most fundamental details ("Am I sending the thing I
wanted to?")
Doing this once or twice, occasionally, is OK. Everyone makes
mistakes every so often. Doing it repeatedly, on a nearly daily basis,
over a period of a couple of months, is simply unacceptable.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Our so-called leaders speak/with words they try to jail ya/ ---
They subjugate the meek/but it's the rhetoric of failure.
signature.asc
Description: Digital signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Trial Patch
On Tue, Sep 09, 2014 at 05:16:19PM -0400, nick wrote:
>
>
> On 14-09-09 12:40 PM, valdis.kletni...@vt.edu wrote:
> > On Tue, 09 Sep 2014 11:52:20 -0400, Nick Krause said:
> >
> >> I understand that , sorry Guys. I am going to fix this later including
> >> my spell checks.
> >
> > Don't bother.
> >
> Valdis,
> I am sending this in again fixed and working. I also looked at your complain
> about write_nic_byte and this
> seems to be there if this succeeds.
You've *still* got the spelling errors in there. This is a symptom
of the fundamental reason that your reputation is appalling -- you are
sloppy in your work. You miss (or ignore) details, even small easy
ones like fixing up the capitalisation of NULL and the spelling on the
same line. This sloppiness extends to not understanding the code
you're trying to change, not thinking it through, not compiling it
before it goes out, not testing it properly before it goes out.
Concentrate on the details. There are lots of details, and you need
to get them *all* right. If someone like Valdis says "you need to fix
this, this and this", fix *everything*. Print out the email, use a
highlighter pen to indicate everything that needs fixing. Put a tick
by every item when you've dealt with it. Don't even *think* about
posting a new revision unless you've got a tick next to every single
highlighter mark.
If someone asks you a question, like "what happens if the condition
in $line_number is true?", this is intended to make you stop and
think. The questions are leading ones, and are trying to make you see
for yourself why there is a problem in your code. The way things are
at the moment, if you look at one of those questions, and answer it,
and the answer *isn't* " bad thing will happen", then you've
missed the point of the question, and you need to look at it harder.
Not answering the question is not an option at this point.
Hugo.
> Nick
> >From 1d6378589ab97cc646e2a3717413077453e4e80b Mon Sep 17 00:00:00 2001
> From: Nicholas Krause
> Date: Mon, 8 Sep 2014 21:30:37 -0400
> Subject: [PATCH] staging: Fix Null check for allocating skb in
> r8192E_firmware.c
>
> This patch checks in fw_download_code for if the allocated skb is
> NULl. Further more if the skb is null and we are in the loop,
> clean up and dequeune the skb quenue. In additon return false
> directly in the if statement and return true by itself removing
> rt_status to improve the code's readablitiy of return statements
> in fw_download_code.
> Signed-off-by: Nicholas Krause
> ---
> drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> index 1a95d1f..6988e1c 100644
> --- a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> +++ b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> @@ -36,7 +36,6 @@ static bool fw_download_code(struct net_device *dev, u8
> *code_virtual_address,
>u32 buffer_len)
> {
> struct r8192_priv *priv = rtllib_priv(dev);
> - boolrt_status = true;
> u16 frag_threshold;
> u16 frag_length, frag_offset = 0;
> int i;
> @@ -61,6 +60,10 @@ static bool fw_download_code(struct net_device *dev, u8
> *code_virtual_address,
> }
>
> skb = dev_alloc_skb(frag_length + 4);
> + if (skb == NULL) {
> +
> skb_queue_purge(&priv->rtllib->skb_waitQ[TXCMD_QUEUE]);
> + return false;
> + }
> memcpy((unsigned char *)(skb->cb), &dev, sizeof(dev));
> tcb_desc = (struct cb_desc *)(skb->cb + MAX_DEV_ADDR_SIZE);
> tcb_desc->queue_index = TXCMD_QUEUE;
> @@ -99,7 +102,7 @@ static bool fw_download_code(struct net_device *dev, u8
> *code_virtual_address,
>
> write_nic_byte(dev, TPPoll, TPPoll_CQ);
>
> - return rt_status;
> + return true;
> }
>
> static bool CPUcheck_maincodeok_turnonCPU(struct net_device *dev)
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Comic Sans goes into a bar, and the barman says, "We don't ---
serve your type here."
signature.asc
Description: Digital signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Rep Improvement
On Sun, Sep 07, 2014 at 08:53:47PM +0200, Carlo Caione wrote: > On Sun, Sep 07, 2014 at 07:06:37PM +0100, Hugo Mills wrote: > > On Sun, Sep 07, 2014 at 01:26:20PM -0400, nick wrote: > > > Hey Guys, > > > I seem to be unable to read the list now :(. > > > >Assuming you're talking about the linux-kernel list, you've > > probably been unsubbed by the mailing list software on vger. It does > > this if it gets too many errors from your mail server. This can happen > > with even a short transient outage that you wouldn't otherwise notice > > -- the list software has something of a hair trigger on these matters. > > It happens to everyone at some point... > > > >I would suggest simply resubscribing, and only start worrying about > > it if you can't resubscribe. > > He was banned. From posting, yes. But from reading as well? Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Great oxymorons of the world, no. 6: Mature Student --- signature.asc Description: Digital signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Rep Improvement
On Sun, Sep 07, 2014 at 01:26:20PM -0400, nick wrote: > Hey Guys, > I seem to be unable to read the list now :(. Assuming you're talking about the linux-kernel list, you've probably been unsubbed by the mailing list software on vger. It does this if it gets too many errors from your mail server. This can happen with even a short transient outage that you wouldn't otherwise notice -- the list software has something of a hair trigger on these matters. It happens to everyone at some point... I would suggest simply resubscribing, and only start worrying about it if you can't resubscribe. Hugo. > I am trying to improve my rep here and it seems impossible after > my ban. I would like to help out here and if anybody has any work, no matter > how simple I would be glad to > do it. > Nick > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- A cross? Oy vey, have you picked the wrong vampire! --- signature.asc Description: Digital signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Test Hardware
On Sat, Aug 30, 2014 at 04:47:07PM -0400, nick wrote:
> Hey Guys,
> I am wondering what test system(s)/hardware specs I need for testing btrfs
> code as I am wondering
> due to thinking about a future budget for it.
If your current hardware can do virtualisation, and you have a few
(tens of) gigabytes of free disk space, then you don't need anything
more. You can set up a virtual machine with a single disk image for
the OS files, install a Linux distribution of your choice on it, and
then create a bunch of sparse disk images:
$ truncate -s 10G test-image.{1,2,3,4}
Pass those to the VM as disk images, and you'll have four 10G disks
in the VM to run xfstests on.
I recommend using qemu for this, because once you've done the base
install, you can use the -kernel, -append and -initrd options to the
qemu-system-x86_64 command to pass your test kernel directly to the
VM. This bypasses the BIOS emulation, and speeds up the boot process
by a few seconds.
The other thing I recommend doing is taking a copy of the base disk
image after you've done the basic OS install -- that way, if something
goes wrong, you can just delete the original and restore from the
backup.
If your machine doesn't have virtualisation support (and most
machines made in the last few years do), then you can still do the
above, but it'll just run rather more slowly.
The above will take a few hours of fiddling and reading through
qemu options, but once it's done, you can write a one-liner shell
script to start your test VM, and you're all ready to run.
Hugo.
> Cheers Nick
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Great oxymorons of the world, no. 6: Mature Student ---
signature.asc
Description: Digital signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
