public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	xiaosuo@gmail.com, tim.gardner@canonical.com,
	torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH 0/3] splice fixes
Date: Thu, 08 Jul 2010 19:30:42 +0200	[thread overview]
Message-ID: <4C360B42.8070909@kernel.dk> (raw)
In-Reply-To: <20100708102544.2e4697f8.akpm@linux-foundation.org>

On 08/07/10 19.25, Andrew Morton wrote:
> On Thu, 08 Jul 2010 15:38:22 +0200 Jens Axboe <axboe@kernel.dk> wrote:
> 
>>>> However this:
>>>>
>>>> commit 4f9078afb4e083e033aafbbfabe729cb3832aa42
>>>> Author: Changli Gao <xiaosuo@gmail.com>
>>>> Date:   Tue Jun 29 13:09:18 2010 +0200
>>>>
>>>>     splice: direct_splice_actor() should not use pos in sd
>>>>
>>>> went into mainline without a cc:stable tag.
>>>
>>> I will send an email to stable@.
>>
>> BTW, it's not in mainline yet. I know I forgot to mark it as stable,
>> but I can't tell them to include it before it's in mainline.
> 
> You could redo the changelog then.  But stable@kernel.org is cc'ed on
> these emails and they're splendid chaps ;)

But then the Linus monster ends up shouting at me, so I'll rather
take a little stable abuse :-)

What I've done in the past is just send stable@ a list of commits
once they are upstream. Less work for them. Best is remembering
the stable CC in the commit, but...

-- 
Jens Axboe


      reply	other threads:[~2010-07-08 17:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 11:08 [PATCH 0/3] splice fixes Miklos Szeredi
2010-06-29 11:09 ` [PATCH 1/3] splice: direct_splice_actor() should not use pos in sd Miklos Szeredi
2010-06-29 11:10 ` [PATCH 2/3] splice: check f_mode for seekable file Miklos Szeredi
2010-06-29 11:13 ` [PATCH 3/3] splice: fix misuse of SPLICE_F_NONBLOCK Miklos Szeredi
2010-06-29 11:15 ` [PATCH 0/3] splice fixes Jens Axboe
2010-06-29 12:05   ` Miklos Szeredi
2010-06-29 12:05     ` Jens Axboe
2010-07-07 20:38       ` Andrew Morton
2010-07-08 13:36         ` Jens Axboe
2010-07-08 13:38           ` Jens Axboe
2010-07-08 17:25             ` Andrew Morton
2010-07-08 17:30               ` Jens Axboe [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=4C360B42.8070909@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=stable@kernel.org \
    --cc=tim.gardner@canonical.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xiaosuo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox