From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Dave Airlie <airlied@gmail.com>, Christoph Hellwig <hch@lst.de>,
Damien Le Moal <damien.lemoal@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] Public i915 CI shardruns are disabled
Date: Tue, 2 Mar 2021 17:01:26 -0800 [thread overview]
Message-ID: <CAHk-=wjmKrGZ+WaBpEb0CbGw7SjRCw1+yjufVa7++5PpLj69Lw@mail.gmail.com> (raw)
In-Reply-To: <f436251f-2eab-df40-7d0a-0f32b40f5996@kernel.dk>
On Tue, Mar 2, 2021 at 4:36 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> Or if you want a pull, just let me know. Have another misc patch to
> flush out anyway that doesn't belong in any of my usual branches.
Ok, if you have something else pending anyway, let's do that. Send me
the pull request, and I'll take it asap.
Thanks,
Linus
next prev parent reply other threads:[~2021-03-03 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e12dfaac0aa242f4a10d8c5b920a98db@intel.com>
[not found] ` <51946a94b1154605bd7dda2c77ab12fc@intel.com>
[not found] ` <fb8a2d722d4b4c008eeb1ffae87233be@intel.com>
[not found] ` <CAPM=9tzLJAgjo=+JCNJrVaz3RY3D66tG+zdw_nCCTQGSwFbwCg@mail.gmail.com>
[not found] ` <CAHk-=whxZJXkuvX2j56QH6ANA_girjWK3nQCPJGuOWwfYEgtag@mail.gmail.com>
[not found] ` <CAPM=9twngQ=T6WgJBVje9PUtYrSa4LyZgsMZKEykCRc_MObrHw@mail.gmail.com>
2021-03-02 23:56 ` Linus Torvalds
2021-03-03 0:15 ` Jens Axboe
[not found] ` <f436251f-2eab-df40-7d0a-0f32b40f5996@kernel.dk>
2021-03-03 1:01 ` Linus Torvalds [this message]
2021-03-03 1:18 ` Jens Axboe
2021-03-03 2:48 ` Linus Torvalds
2021-03-03 9:38 ` Sarvela, Tomi P
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='CAHk-=wjmKrGZ+WaBpEb0CbGw7SjRCw1+yjufVa7++5PpLj69Lw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=chaitanya.kulkarni@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-mm@kvack.org \
--cc=tomi.p.sarvela@intel.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