On Wed, Nov 06, 2019 at 11:39:31AM -0800, Drew Fustini wrote: > On Tue, Nov 05, 2019 at 10:04:26AM +0800, Kent Gibson wrote: > > Allow pull up/down bias to be set on output lines. > > Use case is for open source or open drain applications where > > internal pull up/down may conflict with external biasing. > > > > Signed-off-by: Kent Gibson <warthog618@xxxxxxxxx> > > --- > > drivers/gpio/gpiolib.c | 8 ++++++-- > > 1 file changed, 6 insertions(+), 2 deletions(-) > > I'm not sure if I am doing something wrong but I can't seem to apply this patch > from the series. > > I checked out brgl/gpio/for-next. I opened this mailbox from lore in mutt: > https://lore.kernel.org/linux-gpio/20191105231533.GA3478@sol/t.mbox.gz > > And then I saved each message in the v6 series so I could run 'git am' on each. > I thought I should be able to run git am on the whole mailbox file but I wasn't > sure if the cover letter and replies would cause a problem. > > I'd appreciate any suggestions as to how I can resolve this: > > pdp7@x1:~/linux$ git checkout -b brgl-gpio-for-next brgl/gpio/for-next As per the cover note, v6 is based on brgl/gpio/for-kent, not brgl/gpio/for-next: The changes from v5: - rebased onto Bart's gpio/for-kent branch. That is the only diff between v5 and v6. Ironically you should be applying v5 to your branch :) Specifically, in my branch the v6 patch is applied to e812692b6e9c (brgl/gpio/for-kent) gpio: rcar: Use proper irq_chip name which is still the HEAD at time of writing. Applying the patch to for-next also breaks for me at 0004, so your patches are probably ok. You aren't the only one wondering if there is an easier way to apply patches from lore, especially when there are additional replies in the thread. To write my demo showing how anyone, not just those that received the patches by mail, can rebase v5 onto for-kent to get v6, I ended up downloading the mbox.gz, and unzipping and removing the cruft from it. Fortunately the mbox is chronological, so it was just removing the cover note and then everything after patch 7. Surely there is a better way to do this? Is there a filter for lore or some tool out there that can filter the returned mbox for you? Cheers, Kent.