From: Joel Stanley <joel@jms.id.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/6] ARM: config: Refresh multi v7
Date: Thu, 16 Sep 2021 07:31:21 +0000 [thread overview]
Message-ID: <CACPK8Xf=chwyvLXjyoDt3TvMWsMfUL76-e8Y3ch3aL+9FrsWWg@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0r2w_9mhZ7_-dVJ4-Z=wJk1GAwiK5QpUFZiSuG+zDE+A@mail.gmail.com>
On Tue, 14 Sept 2021 at 14:03, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Tue, Sep 14, 2021 at 10:31 AM Joel Stanley <joel@jms.id.au> wrote:
> > On Tue, 15 Jun 2021 at 01:14, Joel Stanley <joel@jms.id.au> wrote:
> > >
> > >
> > > https://lore.kernel.org/linux-arm-kernel/20210608103833.598348-1-joel@jms.id.au/
> > >
> > > This refreshes the multi v7 defconfig, broken down to show why symbols
> > > are coming and going.
> > >
> > > There are a few drivers that were intended to be part of the config that
> > > are currently disabled, which will once again be tested.
> > >
> > > Joel Stanley (6):
> > > ARM: config: multi v7: Drop unavailable options
> > > ARM: config: multi v7: Clean up enabled by default options
> > > ARM: config: multi v7: Add renamed symbols
> > > ARM: config: multi v7: Enable dependancies
> > > ARM: config: mutli v7: Reenable FB dependency
> > > ARM: config: multi v7: Regenerate defconifg
> >
> > I think I assumed this would be picked up, but I'm not sure why I thought that.
> >
> > Do you want me to send a pull request for v5.16?
>
> Ah right, I think I planned to merge them but then forgot about it as it
> was not in patchwork. If you want to be sure we get to something, best
> send it to soc@kernel.org so we at least remember to take a look.
Thanks for the reminder, I really appreciate how quickly you respond
when something gets sent there.
> > It would be handy to have these two patches in sooner rather than later:
> >
> > > ARM: config: multi v7: Enable dependancies
> > > ARM: config: mutli v7: Reenable FB dependency
>
> I applied these directly to the arm/fixes branch now.
>
> Please rebase the rest on top of v5.15-rc1 or that branch (whichever works
> better for you), and send them as separate patches or a pull request to
> soc@kernel.org.
Will do. Thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-09-16 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:14 [PATCH v3 0/6] ARM: config: Refresh multi v7 Joel Stanley
2021-06-15 1:14 ` [PATCH v3 1/6] ARM: config: multi v7: Drop unavailable options Joel Stanley
2021-06-15 1:14 ` [PATCH v3 2/6] ARM: config: multi v7: Clean up enabled by default options Joel Stanley
2021-06-15 1:14 ` [PATCH v3 3/6] ARM: config: multi v7: Add renamed symbols Joel Stanley
2021-06-15 1:14 ` [PATCH v3 4/6] ARM: config: multi v7: Enable dependancies Joel Stanley
2021-06-15 1:14 ` [PATCH v3 5/6] ARM: config: mutli v7: Reenable FB dependency Joel Stanley
2021-06-15 1:14 ` [PATCH v3 6/6] ARM: config: multi v7: Regenerate defconifg Joel Stanley
2021-09-14 8:31 ` [PATCH v3 0/6] ARM: config: Refresh multi v7 Joel Stanley
2021-09-14 14:03 ` Arnd Bergmann
2021-09-16 7:31 ` Joel Stanley [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='CACPK8Xf=chwyvLXjyoDt3TvMWsMfUL76-e8Y3ch3aL+9FrsWWg@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).