From: Stafford Horne <shorne@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>,
openrisc@lists.librecores.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] openrisc: update config files
Date: Thu, 29 Sep 2022 14:30:18 +0000 [thread overview]
Message-ID: <YzWr+mmtLy2DRYEA@oscomms1> (raw)
In-Reply-To: <YzWp+p+1V1UmCAb3@oscomms1>
Hello,
On Thu, Sep 29, 2022 at 02:21:46PM +0000, Stafford Horne wrote:
> On Thu, Sep 29, 2022 at 12:14:58PM +0200, Lukas Bulwahn wrote:
> > Clean up config files by:
> > - removing configs that were deleted in the past
> > - removing configs not in tree and without recently pending patches
> > - adding new configs that are replacements for old configs in the file
Not all of these apply to this patch. Can you on mention what you changes you
are doing here?
> > For some detailed information, see Link.
> >
> > Link: https://lore.kernel.org/kernel-janitors/20220929090645.1389-1-lukas.bulwahn@gmail.com/
> >
This extra newline is not need.
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
> Hello,
>
> Thanks for the patch this looks fine to me. Usually I just generate this
> defcnfigs using make savedefconfig. If there is some better way which
> doesn't generate the file with the # comment's I haven't found it.
>
> I will queue this.
Actually..
About the subject 'openrisc: update config files' and description. Can you be
more specific about what updates you are making for this patch?
For example: remove comments from config files.
-Stafford
> > ---
> > arch/openrisc/configs/or1ksim_defconfig | 5 -----
> > arch/openrisc/configs/simple_smp_defconfig | 4 ----
> > 2 files changed, 9 deletions(-)
> >
> > diff --git a/arch/openrisc/configs/or1ksim_defconfig b/arch/openrisc/configs/or1ksim_defconfig
> > index 6e1e004047c7..af1164807206 100644
> > --- a/arch/openrisc/configs/or1ksim_defconfig
> > +++ b/arch/openrisc/configs/or1ksim_defconfig
> > @@ -19,9 +19,6 @@ CONFIG_NET=y
> > CONFIG_PACKET=y
> > CONFIG_UNIX=y
> > CONFIG_INET=y
> > -# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
> > -# CONFIG_INET_XFRM_MODE_TUNNEL is not set
> > -# CONFIG_INET_XFRM_MODE_BEET is not set
> > # CONFIG_INET_DIAG is not set
> > CONFIG_TCP_CONG_ADVANCED=y
> > # CONFIG_TCP_CONG_BIC is not set
> > @@ -34,7 +31,6 @@ CONFIG_DEVTMPFS=y
> > CONFIG_DEVTMPFS_MOUNT=y
> > # CONFIG_PREVENT_FIRMWARE_BUILD is not set
> > # CONFIG_FW_LOADER is not set
> > -CONFIG_PROC_DEVICETREE=y
> > CONFIG_NETDEVICES=y
> > CONFIG_ETHOC=y
> > CONFIG_MICREL_PHY=y
> > @@ -52,4 +48,3 @@ CONFIG_SERIAL_OF_PLATFORM=y
> > # CONFIG_DNOTIFY is not set
> > CONFIG_TMPFS=y
> > CONFIG_NFS_FS=y
> > -# CONFIG_ENABLE_MUST_CHECK is not set
> > diff --git a/arch/openrisc/configs/simple_smp_defconfig b/arch/openrisc/configs/simple_smp_defconfig
> > index ff49d868e040..84ca3203af9c 100644
> > --- a/arch/openrisc/configs/simple_smp_defconfig
> > +++ b/arch/openrisc/configs/simple_smp_defconfig
> > @@ -27,9 +27,6 @@ CONFIG_NET=y
> > CONFIG_PACKET=y
> > CONFIG_UNIX=y
> > CONFIG_INET=y
> > -# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
> > -# CONFIG_INET_XFRM_MODE_TUNNEL is not set
> > -# CONFIG_INET_XFRM_MODE_BEET is not set
> > # CONFIG_INET_DIAG is not set
> > CONFIG_TCP_CONG_ADVANCED=y
> > # CONFIG_TCP_CONG_BIC is not set
> > @@ -60,5 +57,4 @@ CONFIG_SERIAL_OF_PLATFORM=y
> > CONFIG_TMPFS=y
> > CONFIG_NFS_FS=y
> > CONFIG_XZ_DEC=y
> > -# CONFIG_ENABLE_MUST_CHECK is not set
> > # CONFIG_RCU_TRACE is not set
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2022-09-29 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 10:14 [PATCH] openrisc: update config files Lukas Bulwahn
2022-09-29 14:21 ` Stafford Horne
2022-09-29 14:30 ` Stafford Horne [this message]
2022-09-29 15:07 ` Geert Uytterhoeven
2022-09-29 16:27 ` Stafford Horne
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=YzWr+mmtLy2DRYEA@oscomms1 \
--to=shorne@gmail.com \
--cc=jonas@southpole.se \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=openrisc@lists.librecores.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).