From: Lee Jones <lee.jones@linaro.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Alistair Francis <alistair@alistair23.me>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Robert Marko <robert.marko@sartura.hr>
Subject: Re: linux-next: manual merge of the char-misc tree with the mfd tree
Date: Wed, 2 Mar 2022 08:49:29 +0000 [thread overview]
Message-ID: <Yh8vmWeW+sPz0DdD@google.com> (raw)
In-Reply-To: <Yh6N4mWCfHtlBM07@kroah.com>
On Tue, 01 Mar 2022, Greg KH wrote:
> > > How do you want to see this merged?
> >
> > The plan is for the whole set to be merged together via MFD.
> >
> > All of the other maintainers have now Acked, so it's ready to go:
> >
> > https://lore.kernel.org/all/20220131133049.77780-1-robert.marko@sartura.hr/
> >
> > Looking at the diff, I'm not entirely sure why you took it in the
> > first place?
>
> As I mentioned above, someone else asked me to as it was sitting around
> for quite a while with no movement.
Okay, just went to investigate.
The set hasn't been merged because it is missing a DT Ack from Rob.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-03-02 8:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 8:39 linux-next: manual merge of the char-misc tree with the mfd tree Stephen Rothwell
2022-02-28 9:01 ` Lee Jones
2022-02-28 10:46 ` Greg KH
2022-02-28 12:46 ` Lee Jones
2022-02-28 21:26 ` Greg KH
2022-03-01 9:37 ` Lee Jones
2022-03-01 10:35 ` Greg KH
2022-03-01 10:54 ` Lee Jones
2022-03-01 21:19 ` Greg KH
2022-03-02 8:00 ` Lee Jones
2022-03-02 8:49 ` Lee Jones [this message]
2022-03-02 10:13 ` Robert Marko
2022-03-01 23:09 ` Robert Marko
2022-03-02 8:37 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2013-02-04 5:12 Stephen Rothwell
2013-02-04 18:27 ` Greg KH
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=Yh8vmWeW+sPz0DdD@google.com \
--to=lee.jones@linaro.org \
--cc=alistair@alistair23.me \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).