mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
	michal.simek@xilinx.com, git@xilinx.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Greg Ungerer <gerg@linux-m68k.org>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>,
	Raju Kumar Pothuraju <rajukumar.pothuraju@amd.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Thippeswamy Havalige <thippeswamy.havalige@amd.com>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH 0/3] microblaze: Defconfig updates
Date: Wed, 15 Nov 2023 13:53:26 +0100	[thread overview]
Message-ID: <3eea894a-f8c4-4f9a-9d11-3ed41bed3ee6@amd.com> (raw)
In-Reply-To: <cover.1698155190.git.michal.simek@amd.com>



On 10/24/23 15:46, Michal Simek wrote:
> Hi,
> 
> I have put together small series based on patches I found in Xilinx/AMD
> Linux tree which will be good to send out.
> The first patch is just synchronization to match the latest Kconfig layout.
> 
> Thanks,
> Michal
> 
> 
> Michal Simek (1):
>    microblaze: Align defconfig with latest Kconfig layout
> 
> Radhey Shyam Pandey (1):
>    microblaze: defconfig: Enable the Marvell phy driver
> 
> Raju Kumar Pothuraju (1):
>    microblaze: Enable options to mount a rootfs via NFS
> 
>   arch/microblaze/configs/mmu_defconfig | 13 +++++++------
>   1 file changed, 7 insertions(+), 6 deletions(-)
> 

Applied.
M

      parent reply	other threads:[~2023-11-15 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 13:46 Michal Simek
2023-10-24 13:46 ` [PATCH 1/3] microblaze: Align defconfig with latest Kconfig layout Michal Simek
2023-10-24 13:46 ` [PATCH 2/3] microblaze: Enable options to mount a rootfs via NFS Michal Simek
2023-10-24 13:46 ` [PATCH 3/3] microblaze: defconfig: Enable the Marvell phy driver Michal Simek
2023-11-15 12:53 ` Michal Simek [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=3eea894a-f8c4-4f9a-9d11-3ed41bed3ee6@amd.com \
    --to=michal.simek@amd.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=gerg@linux-m68k.org \
    --cc=git@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=radhey.shyam.pandey@xilinx.com \
    --cc=rajukumar.pothuraju@amd.com \
    --cc=rdunlap@infradead.org \
    --cc=thippeswamy.havalige@amd.com \
    --cc=vbabka@suse.cz \
    /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

all inboxes | Powered by JetHome®