From: <Parthiban.Veerasooran@microchip.com>
To: <oneukum@suse.com>, <steve.glendinning@shawell.net>,
<UNGLinuxDriver@microchip.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: usb: smsc95xx: configure external LEDs function for EVB-LAN8670-USB
Date: Mon, 27 May 2024 11:42:45 +0000 [thread overview]
Message-ID: <677474fd-746c-4b27-a65e-3bff6daa0b01@microchip.com> (raw)
In-Reply-To: <a6c93527-fc78-4182-9341-97e2fe0d1ace@suse.com>
Hi Oliver,
On 27/05/24 1:58 pm, Oliver Neukum wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know
> the content is safe
>
> On 22.05.24 16:08, Parthiban Veerasooran wrote:
>
> Hi,
>
> however you solve this, the descriptors are stored in wire order.
>
>> + if (dev->udev->descriptor.idVendor == 0x184F &&
>> + dev->udev->descriptor.idProduct == 0x0051)
>> + write_buf |= LED_GPIO_CFG_LED_SEL;
>
> This needs to be
>
> if (dev->udev->descriptor.idVendor == cpu_to_le16(0x184F) &&
> dev->udev->descriptor.idProduct == cpu_to_le16(0x0051))
>
> HTH
> Oliver
Thanks for reviewing the patch. This one was already pointed out by
Simon Horman and kernel test robot. I agreed that but unfortunately
there was an another proposal by Woojung with EEPROM. So I asked to
discard this patch proceeding further and sent out another fix patch for
supporting with Woojung's EEPROM proposal.
My request to discard this patch:
---------------------------------
https://lore.kernel.org/netdev/3e2b2b18-4dd9-4b22-9690-01e1bdd44828@microchip.com/
My request to review the other/new patch:
-----------------------------------------
https://lore.kernel.org/netdev/20240523085314.167650-1-Parthiban.Veerasooran@microchip.com/
The above patch has been already reviewed by both Woojung and Simon:
--------------------------------------------------------------------
https://lore.kernel.org/netdev/20240523144056.GO883722@kernel.org/
https://lore.kernel.org/netdev/BL0PR11MB2913CE81AFC08F2D619C3B6CE7F42@BL0PR11MB2913.namprd11.prod.outlook.com/
Hope this clarifies.
Best regards,
Parthiban V
prev parent reply other threads:[~2024-05-27 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 14:08 Parthiban Veerasooran
2024-05-22 16:44 ` Andrew Lunn
2024-05-23 8:51 ` Parthiban.Veerasooran
2024-05-23 12:43 ` Andrew Lunn
2024-05-24 10:48 ` Parthiban.Veerasooran
2024-05-22 18:54 ` Simon Horman
2024-05-23 8:51 ` Parthiban.Veerasooran
2024-05-22 19:52 ` Woojung.Huh
2024-05-23 8:51 ` Parthiban.Veerasooran
2024-05-23 5:42 ` kernel test robot
2024-05-27 8:28 ` Oliver Neukum
2024-05-27 11:42 ` Parthiban.Veerasooran [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=677474fd-746c-4b27-a65e-3bff6daa0b01@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.com \
--cc=steve.glendinning@shawell.net \
/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®