How to resubmit patches in the right way after review fixes?

In case I have submitted a patch and some mistakes were pointed what is the right way of submitting a corrected version?I basically have 2 questions related to patch re-submit. 1.  Is it appropriate to submit a new patch starting a new thread or it's required to reply    to one of the message in

What is the right thing to do if a patch got ignored?

What is the right things to do if a patch got ignored? Is it appropriate to request a feedback by explicitly replying to the thread or ignoring the patch automatically means that it was rejected? If it's possible to request a feedback how long should I before doing that? I'd like to request a

Compile Kernel with -g3 option to have additional debug information

I compiled Kernel with CONFIG_DEBUG_INFO=y, but this set up -g debug level. Is there a way to configure -g3 option? ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re[2]: Kernel bug tracker

tch by myself?   -- Regards, Adverg Ebashinskii    ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re[2]: Kernel bug tracker

  Hi Thomas,   Thanks for the brief explanation of the bugs.   >  i'll hand over my patch as guideline, or as  >  base for own work, or just for review, testing, and posting   If you could share your patch here to understand the problem better I would gladly dig into it.   -- Regards,

Re[6]: Kernel bug tracker

API. But the thing is that I have almost zero knowledge of what actually going on under the hood and how to debug and fix complicated problems related to the Kernel itself.  So this is the reason of my interest precisely  to core subsystems.   -- Regards, Adverg Ebashins

Re[4]: Kernel bug tracker

etails of a specific hardware. So I tried to get into some core subsystems like fs, net, cgroups, etc...    -- Regards, Adverg Ebashinskii    ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/li

MODULE_SUPPORTED_DEVICE macro existed in the Kernel 5.9.16, but got removed

I recently tried to compile my driver developed for the Kernel 5.9.16 using the latest upstream version checked out from git and figured out that there is no more MODULE_SUPPORTED_DEVICE macro.   Could you please give a hint where to look at for the information on why it was removed?   --

Re[2]: Kernel bug tracker

  Hi Anatoly,   Thank you very much for your response. https://bugzilla.kernel.org looks exactly what I was looking for.   -- Regards, Adverg Ebashinskii      ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https

Kernel bug tracker

Hello.   I’m a kernel newbie and try to get involved into the Kernel development. So I’d like to start with small bug fixes related to any subsystem (fs is preferred since I familiar with it the most) or something like that.   Is there some kernel bug tracker where anybody could pick a bug to

Re: Linux Kernel build dpkg-buildpackage error

sfully. -- Regards, Adverg Ebashinskii    ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Linux Kernel build dpkg-buildpackage error

  Hello!   I’m trying to build Linux Kernel from upstream and faced some build error.   Environment:   Ubuntu 20.04  gcc  (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 Linux Kernel 5.8.0-59-generic   Steps to build:   I follow the instructions specified in this site 

[no subject]

Hello!   I’m trying to build Linux Kernel from upstream and faced some build error.   Environment:   Ubuntu 20.04  gcc  (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 Linux Kernel 5.8.0-59-generic   Steps to build:   I follow the instructions specified in this site