From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Serge Semin <fancer.lancer@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
kernel test robot <lkp@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Ramil Zaripov <Ramil.Zaripov@baikalelectronics.ru>,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10 134/717] spi: dw: fix build error by selecting MULTIPLEXER
Date: Thu, 31 Dec 2020 10:25:07 +0100 [thread overview]
Message-ID: <X+2Y8ynC4JgOZvSw@kroah.com> (raw)
In-Reply-To: <20201231091034.bw733orqxwouijkf@mobilestation>
On Thu, Dec 31, 2020 at 12:10:34PM +0300, Serge Semin wrote:
> On Thu, Dec 31, 2020 at 09:51:21AM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Dec 31, 2020 at 11:49:56AM +0300, Serge Semin wrote:
> > > Hello Greg,
> > > The next patch has been created to supersede the one you've applied:
> > > https://lore.kernel.org/linux-spi/20201127144612.4204-1-Sergey.Semin@baikalelectronics.ru/
> > > Mark has already merged it in his repo.
> >
>
> > Ok, so should that one be queued up as well? Let us know the git commit
> > id of it when it reaches Linus's kernel and we will be glad to take it.
>
> I believe it is already there:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7218838109fef61cdec988ff728e902d434c9cc5
> Yeah, it's better to queue that patch up too, otherwise the build
> error will be indeed fixed by the commit you've merged in, but the
> probe procedure will still always fail.
Ok, now queued up, thanks for letting us know.
greg k-h
prev parent reply other threads:[~2020-12-31 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201228125020.963311703@linuxfoundation.org>
2020-12-28 12:42 ` [PATCH 5.10 134/717] spi: dw: fix build error by selecting MULTIPLEXER Greg Kroah-Hartman
2020-12-31 8:49 ` Serge Semin
2020-12-31 8:51 ` Greg Kroah-Hartman
2020-12-31 9:10 ` Serge Semin
2020-12-31 9:25 ` Greg Kroah-Hartman [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=X+2Y8ynC4JgOZvSw@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Ramil.Zaripov@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=broonie@kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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