From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: meghanaprakash@in.ibm.com, brking@linux.vnet.ibm.com,
mchauras@linux.vnet.ibm.com, mamatha4@linux.vnet.ibm.com,
rharwood@redhat.com, mlewando@redhat.com,
Diego Domingos <diegodo@br.ibm.com>
Subject: Re: [PATCH 2/6] ieee1275/powerpc: enables device mapper discovery
Date: Fri, 15 Mar 2024 21:41:41 +0300 [thread overview]
Message-ID: <CAEaD8JPpBCi6-3LGFwniQOhqB-SvdmcCw2SEM2BUBoe8fJ8tmg@mail.gmail.com> (raw)
In-Reply-To: <20230508135840.47765-3-avnish@linux.vnet.ibm.com>
On Mon, May 8, 2023 at 5:01 PM Avnish Chouhan <avnish@linux.vnet.ibm.com> wrote:
>
> From: Diego Domingos <diegodo@br.ibm.com>
>
> This patch enables the device mapper discovery on ofpath.c. Currently,
> when we are dealing with a device like /dev/dm-* the ofpath returns null
> since there is no function implemented to handle this case.
Why is this result incorrect? Does your OFW handle device-mapper? If
it doesn't then the answer to "what is the OFW path of dm-*?" is
"none" and null is the correct return
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2024-03-15 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 13:58 [PATCH 0/6] NVMeoFC support on Grub Avnish Chouhan
2023-05-08 13:58 ` [PATCH 1/6] ieee1275/powerpc: implements fibre channel discovery for ofpathname Avnish Chouhan
2023-05-08 13:58 ` [PATCH 2/6] ieee1275/powerpc: enables device mapper discovery Avnish Chouhan
2024-03-15 4:06 ` Michael Chang via Grub-devel
2024-03-15 17:54 ` Stefan Berger
2024-03-15 18:41 ` Vladimir 'phcoder' Serbinenko [this message]
2023-05-08 13:58 ` [PATCH 3/6] ieee1275: implement FCP methods for WWPN and LUNs Avnish Chouhan
2023-05-08 13:58 ` [PATCH 4/6] ieee1275: change the logic of ieee1275_get_devargs() Avnish Chouhan
2023-05-08 13:58 ` [PATCH 5/6] ieee1275: add support for NVMeoFC Avnish Chouhan
2023-05-08 13:58 ` [PATCH 6/6] ieee1275: ofpath enable NVMeoF logical device translate Avnish Chouhan
2023-05-10 12:27 ` [PATCH 0/6] NVMeoFC support on Grub Daniel Kiper
2023-06-06 12:01 ` avnish
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=CAEaD8JPpBCi6-3LGFwniQOhqB-SvdmcCw2SEM2BUBoe8fJ8tmg@mail.gmail.com \
--to=phcoder@gmail.com \
--cc=brking@linux.vnet.ibm.com \
--cc=diegodo@br.ibm.com \
--cc=grub-devel@gnu.org \
--cc=mamatha4@linux.vnet.ibm.com \
--cc=mchauras@linux.vnet.ibm.com \
--cc=meghanaprakash@in.ibm.com \
--cc=mlewando@redhat.com \
--cc=rharwood@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).