Re: [PATCH 0/1] Add IMR driver for Keem Bay
On Fri, May 01, 2020 at 08:53:34AM +0100, Daniele Alessandrelli wrote: > On Fri, 2020-05-01 at 09:09 +0200, gre...@linuxfoundation.org wrote: > > On Thu, Apr 30, 2020 at 07:49:36PM +, Alessandrelli, Daniele > > wrote: > > > This e-mail and any attachments may contain confidential material > > > for the sole > > > use of the intended recipient(s). Any review or distribution by > > > others is > > > strictly prohibited. If you are not the intended recipient, please > > > contact the > > > sender and delete all copies. > > > > This footer means I delete all of your emails... > > My bad, I replied using the wrong email address (i.e., the one that > adds the footer automatically). Sorry about that :/ > I'll be more careful the next time. > > The original emails (the ones with the cover letter and the patch) were > fine though (unless I did something else wrong). Any advice on how to > have the patch reviewed and eventually merged? > > > > > > > Ok, let me go look at the code...
Re: [PATCH 0/1] Add IMR driver for Keem Bay
On Fri, 2020-05-01 at 09:09 +0200, gre...@linuxfoundation.org wrote: > On Thu, Apr 30, 2020 at 07:49:36PM +, Alessandrelli, Daniele > wrote: > > This e-mail and any attachments may contain confidential material > > for the sole > > use of the intended recipient(s). Any review or distribution by > > others is > > strictly prohibited. If you are not the intended recipient, please > > contact the > > sender and delete all copies. > > This footer means I delete all of your emails... My bad, I replied using the wrong email address (i.e., the one that adds the footer automatically). Sorry about that :/ I'll be more careful the next time. The original emails (the ones with the cover letter and the patch) were fine though (unless I did something else wrong). Any advice on how to have the patch reviewed and eventually merged?
Re: [PATCH 0/1] Add IMR driver for Keem Bay
On Thu, Apr 30, 2020 at 07:49:36PM +, Alessandrelli, Daniele wrote: > This e-mail and any attachments may contain confidential material for the sole > use of the intended recipient(s). Any review or distribution by others is > strictly prohibited. If you are not the intended recipient, please contact the > sender and delete all copies. This footer means I delete all of your emails...
Re: [PATCH 0/1] Add IMR driver for Keem Bay
On Tue, 2020-04-21 at 17:36 +0100, Daniele Alessandrelli wrote: > The following is a patch for a new Intel Movidius SoC, code-named > Keem > Bay. > > Keem Bay needs a driver to disable the Isolated Memory Region (IMR) > set up by the SoC bootloader during early boot. > > If such an IMR is not disabled and some device tries to access it, > the system will reboot. > > Since this driver is SoC-specific and Keem Bay is a new SoC, I was > unsure of where to put this driver. In the end I decided to create a > new 'keembay' directory in 'drivers/soc'. I hope that's reasonable, > if > not, just let me know. > > > Daniele Alessandrelli (1): > soc: keembay: Add Keem Bay IMR driver > > MAINTAINERS | 5 > drivers/soc/Kconfig | 1 + > drivers/soc/Makefile | 1 + > drivers/soc/keembay/Kconfig | 22 + > drivers/soc/keembay/Makefile | 5 > drivers/soc/keembay/keembay-imr.c | 40 > +++ > 6 files changed, 74 insertions(+) > create mode 100644 drivers/soc/keembay/Kconfig > create mode 100644 drivers/soc/keembay/Makefile > create mode 100644 drivers/soc/keembay/keembay-imr.c > Adding some more people (Arnd and linux-arm-kernel ML) in CC in the hope of getting some guidance on how to have this patch merged. I'm a novice, so I wonder if the lack of feedback is because I'm doing something wrong or if I just sent the initial email to the wrong people / ML. I'd appreciate any help you can provide. -- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
