Linux MM tree latest commits
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stefani Seibold <stefani@seibold.net>
Cc: mm-commits@vger.kernel.org, kernel@irasnyder.com, greg@kroah.com
Subject: Re: + kfifo-replace-the-old-non-generic-api-kfifo-fix-scatterlist-usage.patch added to -mm tree
Date: Wed, 2 Jun 2010 13:34:13 -0700	[thread overview]
Message-ID: <20100602133413.9acfa300.akpm@linux-foundation.org> (raw)
In-Reply-To: <1275510551.1294.7.camel@wall-e.seibold.net>

On Wed, 02 Jun 2010 22:29:11 +0200
Stefani Seibold <stefani@seibold.net> wrote:

> 
> Am Mittwoch, den 02.06.2010, 13:19 -0700 schrieb
> akpm@linux-foundation.org:
> > The patch titled
> >      kfifo: fix scatterlist usage
> > has been added to the -mm tree.  Its filename is
> >      kfifo-replace-the-old-non-generic-api-kfifo-fix-scatterlist-usage.patch
> > 
> > Before you just go and hit "reply", please:
> >    a) Consider who else should be cc'ed
> >    b) Prefer to cc a suitable mailing list as well
> >    c) Ideally: find the original patch on the mailing list and do a
> >       reply-to-all to that, adding suitable additional cc's
> > 
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> > 
> > See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> > out what to do about this
> > 
> > The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> > 
> > ------------------------------------------------------
> > Subject: kfifo: fix scatterlist usage
> > From: Ira W. Snyder <kernel@irasnyder.com>
> > 
> > The current kfifo scatterlist implementation will not work with chained
> > scatterlists.  It assumes that struct scatterlist arrays are allocated
> > contiguously, which is not the case when chained scatterlists (struct
> > sg_table) are in use.
> > 
> 
> Why do you have added this?

Because nobody reviewed the code.

> No one had reviewed the code and no one gave
> an ack. I am currently to busy to check this.

And I don't have the bandwidth to track hundreds of maybe, maybe-not
emails stretching over months of time.  So generally I'll just apply
the thing if it looks good so that I can keep track of it and so that
it gets some testing.


      parent reply	other threads:[~2010-06-02 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 20:19 + kfifo-replace-the-old-non-generic-api-kfifo-fix-scatterlist-usage.patch added to -mm tree akpm
     [not found] ` <1275510551.1294.7.camel@wall-e.seibold.net>
2010-06-02 20:34   ` Andrew Morton [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=20100602133413.9acfa300.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=kernel@irasnyder.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=stefani@seibold.net \
    /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