<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors">
    <title>gmane.linux.kernel.mentors</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/902"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/901"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/900"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/899"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/898"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/897"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/896"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/895"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/894"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/893"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/892"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/891"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/890"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/889"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/888"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/887"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/886"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/885"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/884"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.mentors/883"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/902">
    <title>ISO 8601 Timestamp &lt;-&gt; UNIX Timestamp</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/902</link>
    <description>&lt;pre&gt;Hi everyone,

are there any functions to convert from and to ISO 8601 formatted timestamps?

I found
  void time_to_tm(time_t totalsecs, int offset, struct tm *result)
in include/linux/time.h around line 200, which comes close, but the
other way round would be more interesting.

regards
  Dan

&lt;/pre&gt;</description>
    <dc:creator>Dan Luedtke</dc:creator>
    <dc:date>2012-05-20T11:07:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/901">
    <title>Some questions in v6_copy_user_highpage_aliasing</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/901</link>
    <description>&lt;pre&gt;Hi all,

I have traced v6_copy_user_highpage_aliasing in arch/arm/mm/copypage-v6.c
and found some questions.

 72 /*
 73  * Copy the page, taking account of the cache colour.
 74  */
 75 static void v6_copy_user_highpage_aliasing(struct page *to,
 76         struct page *from, unsigned long vaddr)
 77 {
 78         unsigned int offset = CACHE_COLOUR(vaddr);
 79         unsigned long kfrom, kto;
 80

I think the following statement is to solve aliasing problem that
kernel &amp;amp; user address map to the same physical frame. When
the kernel mapping is dirty, writing back is needed before the copy_page()
is used. Because the color bit of user space address &amp;amp; kernel one
may be difference which cause inconsistency. Now, the problem is
what is the scenario of dirty cache. When does the PG_dcache_dirty
set ? In normal copy-on-write case, I think the if clause will be false.

 81         if (test_and_clear_bit(PG_dcache_dirty, &amp;amp;from-&amp;gt;flags))
 82                 __flush_dcache_page(page_mapping(from), from);
 83

The probl&lt;/pre&gt;</description>
    <dc:creator>Gavin Guo</dc:creator>
    <dc:date>2012-05-08T03:40:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/900">
    <title>Timer drivers using clocksource and clockevents api</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/900</link>
    <description>&lt;pre&gt;Hello,

I wrote a virtual timer for a virtual platform. I do not actually have a
timer hardware device, but I have a periodic irq that I can use and I
know the period which every irq occurs. 

The result I get is a working clock source, but it is slow. The driver
is not %100 right as I have little knowledge of clocksource and
clockevents API. Can you help in spotting issues in the below driver?

All the numbers are made up :) I would appreciate guidance for what to
use on clkrate, cycle value, and any other api parameters.

Thanks in advance,
Bahadir


&lt;/pre&gt;</description>
    <dc:creator>Bahadir Balban</dc:creator>
    <dc:date>2012-04-09T21:01:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/899">
    <title>Invitation to connect on LinkedIn</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/899</link>
    <description>&lt;pre&gt;LinkedIn
------------




    Carter Cheng requested to add you as a connection on LinkedIn:
  

------------------------------------------

Greg,

I'd like to add you to my professional network on LinkedIn.

- Carter

Accept invitation from Carter Cheng
http://www.linkedin.com/e/-13f7ym-gz78yq20-a/gUfpE6MtuEhIxgEzB5uqY5tHupjIxRpxsUQoK7Qq/blk/I179014284_75/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYRdRYQe38Qcj0VdP59bSV5hCVTt3xIbPsRc3gNd38McjoLrCBxbOYWrSlI/EML_comm_afe/?hs=false&amp;amp;tok=0rSLxfV1vZml81

View invitation from Carter Cheng
http://www.linkedin.com/e/-13f7ym-gz78yq20-a/gUfpE6MtuEhIxgEzB5uqY5tHupjIxRpxsUQoK7Qq/blk/I179014284_75/3kTnPgUczgNc3ATckALqnpPbOYWrSlI/svi/?hs=false&amp;amp;tok=120Df1qBfZml81

------------------------------------------

Why might connecting with Carter Cheng be a good idea?

Carter Cheng's connections could be useful to you:

After accepting Carter Cheng's invitation, check Carter Cheng's connections to see who else you may know and who you might want an introduction to. Building t&lt;/pre&gt;</description>
    <dc:creator>Carter Cheng via LinkedIn</dc:creator>
    <dc:date>2012-02-28T18:05:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/898">
    <title>Invitation to connect on LinkedIn</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/898</link>
    <description>&lt;pre&gt;LinkedIn
------------




    Frankie onuonga requested to add you as a connection on LinkedIn:
  

------------------------------------------

Greg,

I'd like to add you to my professional network on LinkedIn.

- Frankie

Accept invitation from Frankie onuonga
http://www.linkedin.com/e/-13f7ym-gxp02siu-35/gUfpE6MtuEhIxgEzB5uqY5tHupjIxRpxsUQoK7Qq/blk/I158095177_75/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYRdRYTdP4Rej0Udj59bPtSqQJCmClVbPAVd3cUcz4QcPkLrCBxbOYWrSlI/EML_comm_afe/?hs=false&amp;amp;tok=1BWonvg2BNx541

View invitation from Frankie onuonga
http://www.linkedin.com/e/-13f7ym-gxp02siu-35/gUfpE6MtuEhIxgEzB5uqY5tHupjIxRpxsUQoK7Qq/blk/I158095177_75/3kTnPsTcjkVc3wRckALqnpPbOYWrSlI/svi/?hs=false&amp;amp;tok=2qEhUzdhNNx541

------------------------------------------

Why might connecting with Frankie onuonga be a good idea?

Frankie onuonga's connections could be useful to you:

After accepting Frankie onuonga's invitation, check Frankie onuonga's connections to see who else you may know and who you might want an int&lt;/pre&gt;</description>
    <dc:creator>Frankie onuonga via LinkedIn</dc:creator>
    <dc:date>2012-01-21T18:57:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/897">
    <title>Re: tcp/ip</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/897</link>
    <description>&lt;pre&gt;Thank you everyone!
I will definitely read some of those suggestions before opening the source
again.

Thanks,
Johan

2012/1/15 François-Frédéric Ozog &amp;lt;ff&amp;lt; at &amp;gt;ozog.com&amp;gt;

_______________________________________________
Kernel-mentors mailing list
Kernel-mentors&amp;lt; at &amp;gt;selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
&lt;/pre&gt;</description>
    <dc:creator>Johan Nestaas</dc:creator>
    <dc:date>2012-01-16T06:19:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/896">
    <title>Re: Kernel-mentors Digest, Vol 72, Issue 2</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/896</link>
    <description>&lt;pre&gt;hi john,

Please follow the book "


   1. *TCP/IP Illustrated, Volume 3: TCP for Transactions, HTTP, NNTP, and
   the UNIX Domain Protocols &amp;lt;http://www.kohala.com/start/tcpipiv3.html&amp;gt;*,
   Addison-Wesley, 1996.

It will help you a lot.

Thanks &amp;amp; Regards

Sanjeev

On Sun, Jan 15, 2012 at 11:30 PM, &amp;lt;kernel-mentors-request&amp;lt; at &amp;gt;selenic.com&amp;gt;wrote:




&lt;/pre&gt;</description>
    <dc:creator>sanjeev</dc:creator>
    <dc:date>2012-01-16T06:11:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/895">
    <title>RE: tcp/ip</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/895</link>
    <description>&lt;pre&gt;I strongly suggest you read « Understanding Linux Network Internals.

 

The networking stack as a separate, huge beast. You could be a skilled disk
driver writer and still have absolutely no clue how the stack works. Another
mega beast is USB

 

Trying to understand it from source code is NOT an option, unless you have a
few years ;-)

 

 

De : kernel-mentors-bounces&amp;lt; at &amp;gt;selenic.com
[mailto:kernel-mentors-bounces&amp;lt; at &amp;gt;selenic.com] De la part de Johan Nestaas
Envoyé : dimanche 15 janvier 2012 11:36
À : kernel-mentors&amp;lt; at &amp;gt;selenic.com
Objet : tcp/ip

 

Hi,


Sorry if this is too newb of a question for the mailing list, but I tried
the kernelnewbies irc chat and no one was responding. Maybe someone could
direct me to a proper mailing list if this isn't the right place.

 

I've been trying to follow the latest kernel source of the tcp/ip stack but
I feel overwhelmed and I don't know the best file to start reading from.
Right now I'm reading linux/net/ipv4/af_inet.c but I have a feeling this is
not the best place &lt;/pre&gt;</description>
    <dc:creator>François-Frédéric Ozog</dc:creator>
    <dc:date>2012-01-15T21:39:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/894">
    <title>Re: tcp/ip</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/894</link>
    <description>&lt;pre&gt;printk is your friend!  Just start putting it in places once you read those articles and you'll start to get it

-stv


On Jan 15, 2012, at 3:33, sumeet gandhare &amp;lt;sumeetgandhare&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

_______________________________________________
Kernel-mentors mailing list
Kernel-mentors&amp;lt; at &amp;gt;selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
&lt;/pre&gt;</description>
    <dc:creator>Steve Iribarne</dc:creator>
    <dc:date>2012-01-15T19:12:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/893">
    <title>Re: tcp/ip</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/893</link>
    <description>&lt;pre&gt;have a look at this link on kernelnewbies

http://kernelnewbies.org/Networking?action=AttachFile&amp;amp;do=get&amp;amp;target=hacking_the_wholism_of_linux_net.txt

HTH,

Regards,
Sumeet

On Sun, Jan 15, 2012 at 4:05 PM, Johan Nestaas &amp;lt;johannestaas&amp;lt; at &amp;gt;gmail.com&amp;gt;wrote:

_______________________________________________
Kernel-mentors mailing list
Kernel-mentors&amp;lt; at &amp;gt;selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
&lt;/pre&gt;</description>
    <dc:creator>sumeet gandhare</dc:creator>
    <dc:date>2012-01-15T11:33:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/892">
    <title>tcp/ip</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/892</link>
    <description>&lt;pre&gt;Hi,

Sorry if this is too newb of a question for the mailing list, but I tried
the kernelnewbies irc chat and no one was responding. Maybe someone could
direct me to a proper mailing list if this isn't the right place.

I've been trying to follow the latest kernel source of the tcp/ip stack but
I feel overwhelmed and I don't know the best file to start reading from.
Right now I'm reading linux/net/ipv4/af_inet.c but I have a feeling this is
not the best place to start. Does anyone have any suggestions? This would
basically be my start to analyzing the kernel source and operating system
data structures, outside of an Operating Systems class I took a semester
ago.

Thanks,
Johan
_______________________________________________
Kernel-mentors mailing list
Kernel-mentors&amp;lt; at &amp;gt;selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
&lt;/pre&gt;</description>
    <dc:creator>Johan Nestaas</dc:creator>
    <dc:date>2012-01-15T10:35:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/891">
    <title>One question about the kernel timer</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/891</link>
    <description>&lt;pre&gt;All

I am reading this code in kernel/timer.
my thought is for most of the timer in tv-&amp;gt;vec, after cascade they
will stay in the same level.
Am I right?

1014static int cascade(struct tvec_base *base, struct tvec *tv, int index)
1015{
1016        /* cascade all the timers from tv up one level */
1017        struct timer_list *timer, *tmp;
1018        struct list_head tv_list;
1019
1020        list_replace_init(tv-&amp;gt;vec + index, &amp;amp;tv_list);
1021
1022        /*
1023         * We are removing _all_ timers from the list, so we
1024         * don't have to detach them individually.
1025         */
1026        list_for_each_entry_safe(timer, tmp, &amp;amp;tv_list, entry) {
1027                BUG_ON(tbase_get_base(timer-&amp;gt;base) != base);
1028                internal_add_timer(base, timer);
1029        }
1030
1031        return index;
1032}

I think this function is trying to move some of the timer to another level.
Since the internal_add_timer() will calculate the hash number based on
the timer-&amp;gt;expire,
so I guess for the ti&lt;/pre&gt;</description>
    <dc:creator>Wizard</dc:creator>
    <dc:date>2012-01-14T15:49:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/890">
    <title>Should I generate inode numbers?</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/890</link>
    <description>&lt;pre&gt;Hello everyone,

I am thinking about a concept for a filesystem (read: kernel-module),
and when studying the sources I found in in include/linux/fs.h

 751 struct inode {
 ...
 771         /* Stat data, not accessed from path walking */
 772         unsigned long           i_ino;

Source: http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=include/linux/fs.h;h=057434af2b900e18745b375b109e52ef03a9c6c0;hb=HEAD#l772

I want to use the blocknumber as inode number to
-keep the code simple
-avoid collisions and
-always know which block of a device an inode can be found in.

When I would my code like intended, and it would be compiled on a 32
bit machine, then unsigned long would be 32 bit. That would cause some
trouble when mounting partitions with more than 2^32 blocks, wouldn't
it?

So, as long as i_ino is not 64 bit (which was already discussed years
ago by some ext4 developers I think), what should I do? Should I
generate inode numbers (e.g. by incrementing a "global" variable) and
check for&lt;/pre&gt;</description>
    <dc:creator>Dan Luedtke</dc:creator>
    <dc:date>2011-12-13T17:43:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/889">
    <title>advice on next step</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/889</link>
    <description>&lt;pre&gt;

Hi guys,
I would like to kindly ask for an extension on the time I gave.I came across a book :
Understanding the Linux Kernel by Daniel P Bovet and Marco Cesati.
I believe to further help i need to go from page on to the end of it.I have already started but i believe with another two weeks all should be on my finger tips.
Thanks again to : vijaitm&amp;lt; at &amp;gt;gmail.com and Greg for the direction.
keep well.

frankie
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.This communication contains confidential information. It is for the exclu&lt;/pre&gt;</description>
    <dc:creator>Frankie Onuong'a</dc:creator>
    <dc:date>2011-12-02T10:15:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/888">
    <title>Re: What should I do when I cant get any response to my patch</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/888</link>
    <description>&lt;pre&gt;
Not really.


I don't really know, try asking the ARM developers about the platform
stuff.

greg k-h
&lt;/pre&gt;</description>
    <dc:creator>Greg KH</dc:creator>
    <dc:date>2011-11-27T09:29:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/887">
    <title>Re: What should I do when I cant get any response to my patch</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/887</link>
    <description>&lt;pre&gt;
I've also expanded that list with few people who I saw linux-kernel list
working on same subarch (in my current understanding of that word). Is
there any other way to find people interested in my patch?


I just wanted to clarify the meaning of subarch.

I have s3c2440 core, which is a part of s3c24xx family which is a part
of Samsung-SoC family which belongs to ARM arch.
So in my case:
ARM is an arch,
Samsung-SoC is a subarch,
s3c24xxis a sub-subarch (or a platform?)

Is my understanding right?

&lt;/pre&gt;</description>
    <dc:creator>Denis Kuzmenko</dc:creator>
    <dc:date>2011-11-26T21:33:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/886">
    <title>Re: What should I do when I cant get any response to my patch</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/886</link>
    <description>&lt;pre&gt;
Yes, it's a great start, but don't let it substitute for common sense :)


I don't know, you should know best based on the patch location and what
hardware is affected here.

good luck,

greg k-h
&lt;/pre&gt;</description>
    <dc:creator>Greg KH</dc:creator>
    <dc:date>2011-11-26T19:55:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/885">
    <title>RE: advice on next step</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/885</link>
    <description>&lt;pre&gt;
Hi.thanks for the advice.I will be sure to remind myself these.please give me about two weeks as I am also in the middle of my end year exams.
thanks,
frankie


La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communicati&lt;/pre&gt;</description>
    <dc:creator>Frankie Onuong'a</dc:creator>
    <dc:date>2011-11-26T19:57:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/884">
    <title>Re: What should I do when I cant get any response to my patch</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/884</link>
    <description>&lt;pre&gt;Hi Greg,

On 11/26/2011 05:19 PM, Greg KH wrote:

So getting recipients list from get_maintainer.pl output is not enough?
What is subarch? Is this a Samsung-SoC or some more specific (s3c, s5p)?


Thank you.

&lt;/pre&gt;</description>
    <dc:creator>Denis Kuzmenko</dc:creator>
    <dc:date>2011-11-26T19:35:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/883">
    <title>Re: What should I do when I cant get any response to my patch</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/883</link>
    <description>&lt;pre&gt;
Send it again, it's so small, I don't see why it wouldn't be accepted.


Please resend, to the maintainer of that file and cc: the subarch
maintainers as well.

Persistence is key.

greg k-h
&lt;/pre&gt;</description>
    <dc:creator>Greg KH</dc:creator>
    <dc:date>2011-11-26T15:19:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.mentors/882">
    <title>What should I do when I cant get any response to my patch</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.mentors/882</link>
    <description>&lt;pre&gt;Hi Linux Mentors.

I've made a patch to add support of LCD W35i for Mini2440 board. Looks
like this is a new version of LCD which is supplied with all new boards.

First time I've posted that patch:

https://lkml.org/lkml/2011/6/13/345
https://lkml.org/lkml/2011/6/14/331

got comments and fixed all things required to be fixed.

I've tried to resend that patch in five months and now I can't get any
replies

https://lkml.org/lkml/2011/11/17/376

I've formed recipients list from the output of get_maintainer.pl script.
This looks like no one is interested in this feature being in mainline?

There is no way I can prove that this feature is needed by many users
but I've received a letter from someone googled W35i support with a
question on how to use that display with Linux.

So suggest me please what should I do next?

Should I email this path to Andrew Morton for inclusion in -mm three?
Or should i just periodically repost that waiting or someone got interested?

&lt;/pre&gt;</description>
    <dc:creator>Denis Kuzmenko</dc:creator>
    <dc:date>2011-11-26T14:02:43</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.kernel.mentors">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.kernel.mentors</link>
  </textinput>
</rdf:RDF>

