All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlim <vlim@gigadevice.com>
To: Michal Simek <michal.simek@amd.com>,
	Michal Simek <monstr@monstr.eu>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: "vigneshr@ti.com" <vigneshr@ti.com>,
	"jagan@amarulasolutions.com" <jagan@amarulasolutions.com>,
	"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
	"vikhyat.goyal@amd.com" <vikhyat.goyal@amd.com>,
	"ashok.reddy.soma@amd.com" <ashok.reddy.soma@amd.com>
Subject: Re: [PATCH 0/4] Enable gigadevice and add new part #s
Date: Thu, 5 Jan 2023 19:47:12 +0000	[thread overview]
Message-ID: <TY0PR06MB56587D992D07C354CCC7946ABBFA9@TY0PR06MB5658.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <2e072563-2151-6f68-4359-7eeb6eaa3ec1@amd.com>

> Regarding the location of the entry, I believe you want me to add the entry in
> the alphabetical order?

Not really. I want to you follow Kconfig layout which is what make savedefconfig
&& cp defconfig configs/<defconfig> is for.

Can you be more specific on this requirement?
I believe this is pertaining to the defconfig files.
Where is the correct line to insert the following entry?
CONFIG_SPI_FLASH_GIGADEVICE=y

Regards,

Victor


  reply	other threads:[~2023-01-06 12:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 22:48 [PATCH 0/4] Enable gigadevice and add new part #s Victor Lim
2022-12-19 22:48 ` [PATCH 1/4] xilinx: zynq: Enable gigadevice Victor Lim
2022-12-19 22:48 ` [PATCH 2/4] arm64: zynqmp: " Victor Lim
2022-12-19 22:48 ` [PATCH 3/4] xilinx: versal: Enable gigadevice parts Victor Lim
2022-12-19 22:48 ` [PATCH 4/4] mtd: spi-nor-ids: add gigadevice part # Victor Lim
2023-01-03 11:02 ` [PATCH 0/4] Enable gigadevice and add new part #s Michal Simek
2023-01-04 18:50   ` Vlim
2023-01-05  7:25     ` Michal Simek
2023-01-05 19:47       ` Vlim [this message]
2023-01-06  7:14         ` Michal Simek
2023-01-06 19:53           ` Vlim
2023-01-09  7:59             ` Michal Simek

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=TY0PR06MB56587D992D07C354CCC7946ABBFA9@TY0PR06MB5658.apcprd06.prod.outlook.com \
    --to=vlim@gigadevice.com \
    --cc=ashok.reddy.soma@amd.com \
    --cc=jagan@amarulasolutions.com \
    --cc=michal.simek@amd.com \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    --cc=vikhyat.goyal@amd.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.