From: Christoph Hellwig <hch@lst.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Sam Protsenko <semen.protsenko@linaro.org>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-janitors@vger.kernel.org, jaharkes@cs.cmu.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
codalist@coda.cs.cmu.edu, coda@cs.cmu.edu,
Praneeth Bajjuri <praneeth@ti.com>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>
Subject: Re: [PATCH v2] codafs: Fix build using bare-metal toolchain
Date: Wed, 21 Nov 2018 17:57:23 +0100 [thread overview]
Message-ID: <20181121165723.GA5980@lst.de> (raw)
In-Reply-To: <CAHp75Vd-ydncUWQtc8ziLpCMJRFCvjV=ueKB0wRgn7W-pnV09Q@mail.gmail.com>
On Wed, Nov 21, 2018 at 06:41:13PM +0200, Andy Shevchenko wrote:
> I'm not sure how you managed to miss people in this list (perhaps by
> default you have suppress all Cc in your Git configuration), but I
> guess we may gently ask Christoph to apply this in case Jan will not
> appear.
I don't really have a relevant tree. You probably want to send it
to Al Viro.
next prev parent reply other threads:[~2018-11-21 16:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 20:27 [PATCH v2] codafs: Fix build using bare-metal toolchain Sam Protsenko
2018-11-21 16:31 ` Sam Protsenko
2018-11-21 16:41 ` Andy Shevchenko
2018-11-21 16:57 ` Christoph Hellwig [this message]
2018-11-21 18:10 ` Jan Harkes
2018-11-21 19:36 ` Sam Protsenko
2018-11-21 19:39 ` Sam Protsenko
2018-11-21 22:48 ` Jan Harkes
2019-01-09 15:45 ` Sam Protsenko
2018-11-22 11:32 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2018-10-29 20:03 Sam Protsenko
2018-10-29 20:05 ` Sam Protsenko
2018-10-29 20:08 ` Andy Shevchenko
2018-10-30 6:34 ` Greg KH
2018-10-30 12:01 ` Sam Protsenko
2018-10-30 13:04 ` Jan Harkes
2018-10-30 18:33 ` Sam Protsenko
2018-10-30 18:39 ` Andy Shevchenko
2018-11-23 20:07 ` Andy Shevchenko
2018-11-26 14:35 ` Sam Protsenko
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=20181121165723.GA5980@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=jaharkes@cs.cmu.edu \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=ruslan.bilovol@gmail.com \
--cc=semen.protsenko@linaro.org \
/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