All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, jesse.brandeburg@intel.com,
	intel-wired-lan@lists.osuosl.org, davem@davemloft.net,
	khc@pm.waw.pl
Subject: Re: [Intel-wired-lan] [PATCH v4] netdevice: use ifmap instead of plain fields
Date: Sat, 04 Mar 2023 18:03:29 +0100	[thread overview]
Message-ID: <CQXRF9CS3SAI.2TU7KF0UR6V7P@vincent-arch> (raw)
In-Reply-To: <20230304080650.74e8d396@hermes.local>

On Sat Mar 4, 2023 at 5:06 PM CET, Stephen Hemminger wrote:
> On Sat,  4 Mar 2023 13:24:33 +0100
> Vincenzo Palazzo <vincenzopalazzodev@gmail.com> wrote:
>
> > clean the code by using the ifmap instead of plain fields,
> > and avoid code duplication.
> > 
> > v4 with some build error that the 0 day bot found while
> > compiling some drivers that I was not able to build on 
> > my machine.
> > 
> > Reported-by: kernel test robot <lkp@intel.com>
> > Link: https://lore.kernel.org/oe-kbuild-all/202303041847.nRrrz1v9-lkp@intel.com/
> > Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
> > ---
>
> Patching cadaver drivers is not worth it.

Mh, what is mean? they are drivers that are not longer
mantained and/or used?

Cheers!

Vincent.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<intel-wired-lan@lists.osuosl.org>, <jesse.brandeburg@intel.com>,
	<khc@pm.waw.pl>, "kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH v4] netdevice: use ifmap instead of plain fields
Date: Sat, 04 Mar 2023 18:03:29 +0100	[thread overview]
Message-ID: <CQXRF9CS3SAI.2TU7KF0UR6V7P@vincent-arch> (raw)
In-Reply-To: <20230304080650.74e8d396@hermes.local>

On Sat Mar 4, 2023 at 5:06 PM CET, Stephen Hemminger wrote:
> On Sat,  4 Mar 2023 13:24:33 +0100
> Vincenzo Palazzo <vincenzopalazzodev@gmail.com> wrote:
>
> > clean the code by using the ifmap instead of plain fields,
> > and avoid code duplication.
> > 
> > v4 with some build error that the 0 day bot found while
> > compiling some drivers that I was not able to build on 
> > my machine.
> > 
> > Reported-by: kernel test robot <lkp@intel.com>
> > Link: https://lore.kernel.org/oe-kbuild-all/202303041847.nRrrz1v9-lkp@intel.com/
> > Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
> > ---
>
> Patching cadaver drivers is not worth it.

Mh, what is mean? they are drivers that are not longer
mantained and/or used?

Cheers!

Vincent.

  reply	other threads:[~2023-03-06 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 12:24 [Intel-wired-lan] [PATCH v4] netdevice: use ifmap instead of plain fields Vincenzo Palazzo
2023-03-04 12:24 ` Vincenzo Palazzo
2023-03-04 16:06 ` [Intel-wired-lan] " Stephen Hemminger
2023-03-04 16:06   ` Stephen Hemminger
2023-03-04 17:03   ` Vincenzo Palazzo [this message]
2023-03-04 17:03     ` Vincenzo Palazzo

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=CQXRF9CS3SAI.2TU7KF0UR6V7P@vincent-arch \
    --to=vincenzopalazzodev@gmail.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=khc@pm.waw.pl \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 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.